Robert Elz <kre(_at_)munnari(_dot_)OZ(_dot_)AU> writes:
Not that I much care of course, as I'm not an nmh user, and don't plan to
be, except that every incpmpatible change is going to make exmh harder to
support.
While any of these changes may be justifiable in isolation,
I'm beginning to worry about their cumulative effect. I think
a very large fraction of people use mh via front ends of one
ilk or another, so tweaking the names and default states of
various command line switches isn't really going to do much
for them except risk breaking their front ends. Also remember
that those who dislike the current default of any switch have
probably got entries in their ~/.mh_profile to override it.
Perhaps it is time for a configuration symbol that controls how
MH-compatible nmh ought to be? Making these changes conditional
on #ifdef STRICT_MH_SWITCHES, or some such, would help cater to
both camps.
regards, tom lane