On Wed, Jan 4, 2012 at 21:51, Jeffrey Honig <address@hidden>
On Wed, Jan 4, 2012 at 21:34, Ken Hornstein <address@hidden>
So I've been looking at removing crud in nmh's autoconf support and mass
of #ifdefs, and I came across the --enable-mhe option.
This defines MHE during the build, and it enables a few bits of MHE
support (some commands get a -build switch, and inc does some extra stuff).
The default has been to build with mh-e support, and I suspect that very
few people have NOT built nmh with mh-e support so I doubt that it is
causing many problems. I propose removing the configure option and associated
#ifdefs so that mh-e support is always included in nmh. Comments?
I'd like to audit them and see if we actually use them (we being mh-e developers). Features that are actually used should always be enabled *and* documented.
Well, that was easy...
The code in inc.c, rnf,cm folder_read.c and mh-profile.man is some audit log stuff not used by mh-e (special audit file).
The -build option in forw.c and repl.c *are* used by mh-e. The documentation for those flags would need to be cleaned up.