> >It's always bugged me that MH/nmh starts to install a new user setup if > >it can't find something it's looking for -- like the MH (.mh_profile) > >file. IMHO, it should simply fail and print an error message that gives > >the pathname of the MH file that it's looking for (that's either the > >setting of the MH envariable, or $HOME/.mh_profile). It could also tell > >the user how to install MH/nmh. The error could say something like: > > >"<progname>: aborting: can't read <pathname-of-MH-file>. Check your MH > >environment variable (if any) or run install-mh to install nmh." > > I vote for that feature.
I guess that I wasn't being brave enough to suggest changing the way that things worked. I'll give it a few days to settle out, and then make the above change if no major objections arise. Jon
