"Jeffrey C Honig" wrote:
When running under mh-e, I set the MHCONTEXT environment variable to
/dev/null. This prevents my mh-e context from confusing my command line
With 1.1 this breaks things.
We could allow MHCONTEXT=/dev/null with the following trivial patch.
Google reveals a script or two that uses this trick. I'm inclined to
apply it (although it seems a bit ugly) -- objections?
I believe that this is a fix for a symptom, not a problem.
There are (or may be) other files that MH opens in directories that are
not writable. The locking system needs to deal with this properly.
I can not remember any examples offhand, it has been a couple years
since I switched to lockf locking. But I can imaging one.
If you have a mail directory (either under ~Mail, or an external
directory) on read-only storage, dot locking will fail. Things like
this are assumed to be part of the flexibility of nmh and should
continue to work.
Jeffrey C. Honig <email@example.com>
GnuPG ID:14E29E13 <http://www.honig.net/jch/key.shtml>
Nmh-workers mailing list