[225] in Zephyr_Bugs
[jik@pit-manager.MIT.EDU: rt 7.2P: zwgc]
daemon@ATHENA.MIT.EDU (Jonathan I. Kamens)
Wed Jan 9 02:36:04 1991
Date: Wed, 9 Jan 91 02:35:47 -0500
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
To: bug-zephyr@ATHENA.MIT.EDU
----- Forwarded message 1
Date: Tue, 8 Jan 91 21:24:56 -0500
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
Sender: jik@pit-manager.MIT.EDU
To: bugs@ATHENA.MIT.EDU
Subject: rt 7.2P: zwgc
System name: pit-manager
Type and version: RTPC-ROMPC 7.2P
Display type: apa16
megapel
What were you trying to do?
Get zwgc to do what it used to do, and have different number
of beeps in different messages.
What's wrong:
It can't be done.
What should have happened:
The new feature of filtering beeps should not have been
implemented without allowing a fallback to the old behavior.
In particular, the implementation I would have preferred would
have been an X resource to toggle the filtering (with the
default to have it enabled), and a variable that can be set in
.zwgc.desc in order to turn it on and off for individual
messages.
jik
----- End of forwarded message 1
----- Forwarded message 2
To: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
Cc: bugs@ATHENA.MIT.EDU
Subject: Re: rt 7.2P: zwgc
In-Reply-To: [6830] in Athena Bugs
Reply-To: marc@MIT.EDU
X-Usmail: Marc Horowitz, 3 Ames Street, Cambridge, MA 02139
X-Phone: (617)225-6458
Date: Tue, 08 Jan 91 21:27:58 EST
From: Marc Horowitz <marc@ATHENA.MIT.EDU>
In particular, the implementation I would have preferred would
have been an X resource to toggle the filtering (with the
default to have it enabled), and a variable that can be set in
.zwgc.desc in order to turn it on and off for individual
messages.
I disagree. I would prefer an implementation which would let you
select a maximum number of beeps (including 0) for any style. This is
easy to implement given zwgc's internals.
Marc
----- End of forwarded message 2
----- Forwarded message 3
Date: Tue, 8 Jan 91 21:36:48 -0500
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
Sender: jik@pit-manager.MIT.EDU
To: marc@MIT.EDU
Cc: bugs@ATHENA.MIT.EDU
In-Reply-To: bugs[6830]
Subject: rt 7.2P: zwgc
Reply-To: marc@MIT.EDU
X-Usmail: Marc Horowitz, 3 Ames Street, Cambridge, MA 02139
X-Phone: (617)225-6458
Date: Tue, 08 Jan 91 21:27:58 EST
From: Marc Horowitz <marc@ATHENA.MIT.EDU>
I disagree. I would prefer an implementation which would let you
select a maximum number of beeps (including 0) for any style. This is
easy to implement given zwgc's internals.
You're right, this sounds like a better implementation. But I still
think that it must be possible to override the resources in your
.zwgc.desc for any individual message.
jik
----- End of forwarded message 3
----- Forwarded message 4
To: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
Cc: marc@MIT.EDU, bugs@ATHENA.MIT.EDU
Subject: Re: rt 7.2P: zwgc
In-Reply-To: [6832] in Athena Bugs
Reply-To: marc@MIT.EDU
X-Usmail: Marc Horowitz, 3 Ames Street, Cambridge, MA 02139
X-Phone: (617)225-6458
Date: Tue, 08 Jan 91 22:56:38 EST
From: Marc Horowitz <marc@ATHENA.MIT.EDU>
>> I disagree. I would prefer an implementation which would let you
>> select a maximum number of beeps (including 0) for any style. This is
>> easy to implement given zwgc's internals.
>>
>> You're right, this sounds like a better implementation. But I still
>> think that it must be possible to override the resources in your
>> .zwgc.desc for any individual message.
That's easy enough, also.
Marc
----- End of forwarded message 4
