[240] in Zephyr_Bugs
[Barr3y.Jaspan@ATHENA.MIT.EDU,bjaspan@ATHENA.MIT.EDU: rt 7.2P: xzwrite man page errors]
daemon@ATHENA.MIT.EDU (Jonathan I. Kamens)
Tue Feb 19 15:49:54 1991
Date: Tue, 19 Feb 91 15:49:27 -0500
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
To: bug-zephyr@ATHENA.MIT.EDU
----- Forwarded message
To: bugs@ATHENA.MIT.EDU
Subject: rt 7.2P: xzwrite man page errors
Date: Fri, 01 Feb 91 00:31:03 EST
From: Barr3y.Jaspan@ATHENA.MIT.EDU, bjaspan@mit.edu <bjaspan@ATHENA.MIT.EDU>
System name: portnoy
Type and version: RTPC-ROMPC 7.2P (1 update(s) to same version)
Display type: apa16
What were you trying to do?
Read the xzwrite man page.
What's wrong:
I found lots of typos and other mistakes (which, of course, I made).
Xzwrite can get its list of destina-
tions from the files .xzwrite.dest, user's home directory.
These files must consist of a list of lines, and each is
That should be .xzwrite.dest, .anyone, and .zephyr.subs. Probably
some nroff confusion.
If the user specifies a destination in the .xzwrite.dest
file with an instance or recipient of "...", xzwrite will
prompt the user to enter an instance or recipient when the
message editor is popped up.
Should be "xzwrite will prompt the user to enter an instance or
recipient when the destination is selected."
For
examples of how to use these resource names, look in
/mit/sipb/usr/lib/app-defaults/XZwrite.)
That should point to /usr/athena/lib/zephyr/XZwrite. In general,
shouldn't there be an Athena app-defaults directory?
options (or resource database specifications). Each should
be preceded by XZwrite* in the user's .Xresources file.
When a command-lie
I have no idea what I meant to type there; perhaps there was a fire
alarm while I was editing the file.
-v (verbose = false)
When true, causes xzwrite to inform the user no one
received a sent message by beeping. This is useful if
the user wants to know if someone logged out between
the time when the editor is popped up (when a PING is
sent) and when the message is actually sent.
A PING is actually only sent when a destination is selected, which
makes this much more useful.
Xzwrite will also look in the user's
.zephyr.vars file to a signature
"for a signature"
tion tables. The following action procedures available to
the user.
"are available to the user"
For examples on how to use these action procedures, look in
/usr/sipb/lib/app-defaults/XZwrite.
Ditto previous comment.
~/.xzwrite.dest
The user's xzwrite destinations list. ~/.anyone The
user's .anyone file. ~/.zephyr.subs The user's zephyr
subscription file.
Clearly the formatting just didn't work.
BUGS
xzwrite occasionally decided to ignore the state of the
"Pings" and "Authentic" menu options
Marc tells me this might be because of an authenticator-caching bug
present in the 7.1 version of the Zephyr library. This bug never
happened to me so I can't really tell if it has gone away. Ask John
Kohl.
What should have happened:
I should have just fixed these, but finding typos takes less effort
than fixing them and I'm tired.
Please describe any relevant documentation references:
xzwrite(1)
----- End of forwarded message
