🚀 go-pugleaf

	There's a few bugs I've seen in 2.3PL11.  Some are just
annoying, some are nasty.  2.4 won't be installed on the systems I use
until it is stable for a while, but I wanted to know if these bugs
were fixed or addressed.  (Or, are they features?)

1) Clobbering files when over quota

	Elm doesn't check the return value of a write to a file, or if
it does, it blithefully ignores it.  If a user is over quota and elm
saves a letter to a file, the letter is not saved.  The letter is then
marked for deletion.  The letter is thus lost.
	If a person reads and modifies a folder in an account which is
over quota, the file is truncated to zero bytes.
	If a write fails, elm should notify the user.  If the file
cannot be written back to the user's directory, elm should exit with
the original file in the tmp directory and a glaring error message.

2) Improper expansion of ~

	In other programs I use ((t)csh, rn, tin, mail, etc) ~ is
expanded to the value of the environmental variable (getenv).  Elm
appears to use the pasword entry of the user's root directory
(getpwuid).
	I understand why elm needs the .elm directory in the user's
root directory, but there's no reason to assume that the user's root
directory and $HOME are the same thing.  If $HOME is defined it should
use that.  (It also seems reasonable to look for or create the Mail
directory.)
	If your elmrc file specifies your mail directory as
$HOME/Mail, elm uses the environmental variable, so it definitely is
aware of what $HOME should be.

3) Deletion of the letter being composed if connection dies and elm
	quits

	/usr/ucb/mail saves such files to dead.letter.  I can usally
get the letter back with the use of ps, grep, a copy, and a kill
signal to the elm process.  But users should not be expected to know
this.  It seems safe to assume that users do not want the letter
they've spent a half hour composing erased.

4) Bugs in saving to ~$USER/Cancelled.mail in send only mode

	elm is kind enough to save the mail body to the file
Cancelled.mail in the user's root directory if invoked in send only
mode.  If you cancel the message, it gives the exit message:

	Message saved in file "$HOME/Cancelled.mail"

Well, it is not saving the file to $HOME/Cancelled.mail.  It is saving
to the user's root directory.	Until afs 4.0/dfs is released, this is
also a security/privacy risk for many users.  (afs permissions are
directory not file based.)
	Also, it would be nice if it saved the header of the letter,
too.

5) Hard coded path in the default user's elmrc file

	Why?

	Thanks!
				Yours,
					Larry Schwimmer
					schwim@xenon.stanford.edu