[145] in Zephyr_Comments
``completely null description''
daemon@ATHENA.MIT.EDU (Mark W. Eichin)
Thu Dec 1 03:02:03 1988
Date: Thu, 1 Dec 88 03:01:28 EST
From: Mark W. Eichin <eichin@ATHENA.MIT.EDU>
To: zephyr-comments@ATHENA.MIT.EDU
The ``completely null description'' message occurs when zwgc would
otherwise create a 0x0 window. Since this would be equivalent to
bit-bucketing the message (as X doesn't HAVE a concept of 0x0 windows,
it is a protocol violation) which could merely be suffering from a
common case of broken $default (or broken user description file)
should this feature be `adjusted' or merely documented better?
Mark Eichin
<eichin@athena.mit.edu>
SIPB Member & Project Athena ``Watchmaker''
encl: 1 forwarded message.
||Date: Tue, 29 Nov 88 23:06:33 EST
||From: Bill Sommerfeld <wesommer@ATHENA.MIT.EDU>
||Message-Id: <8811300406.AA04100@ANUBIS.MIT.EDU>
||To: eichin@ATHENA.MIT.EDU
||Subject: zwgc bug.
||
||I have a "crock" in my .zephyr.desc file which contains the following:
||
|| does $instance
|| match MOTD
|| show
|| $message
|| endshow
|| endmatch
|| enddoes
||
||when I "zwrite wesommer -i motd </dev/null", I get the
||"Completely Null Description for message" pane, instead of a null
||window..
||
|| - Bill
