🚀 go-pugleaf

syd@DSI.COM ponders:
>schwim@Xenon.Stanford.EDU (Rosebud) writes:
[Query on bugs in 2.3PLll asking if 2.4 fixes them]
	
Sydney,
	Thanks for the prompt response!

>>2) Improper expansion of ~
>>	In other programs I use ((t)csh, rn, tin, mail, etc) ~ is
>>expanded to the value of the environmental variable HOME (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.
>This one is a feature.  Elm ignores $HOME, so that when su'd you read
>the right mail file.  Its a choice of one or the other and we chose
>to allow su over $HOME.

	When is that necessary?  filter has everything it needs in the
.elm directory.

>>5) Hard coded path in the default user's elmrc file
>>	Why?
>because....

	On systems with a lot of accounts, it is common for accounts
to switch partitions due to disk space problems.  Elm gives an error
message each time that the Mail directory doesn't exist and asks if
you want to create it.  Of course, you can't becuase the path is
wrong.
	If 2.4 or 3 still hard codes the path, could I suggest that
the program check to see if the path even exists (and possibly that it
matches the user's passwd entry)?  (Or at least make it a compile time
option if this causes problems on some systems?  Or have some way to
have the elmrc file default to a specified variable, such as
$HOME/Mail or even ~/Mail, instead of a hard coded path?)

	As a side note, this one-liner works for (t)csh on elm 2.3PL11:

perl -i -pe 's%^maildir.*%maildir = \$HOME/Mail%;' ~$USER/.elm/elmrc

				Yours,
					Larry Schwimmer
					schwim@xenon.stanford.edu