In mh-utils.el, the variable mh-nmh-p (t when nmh is in
use rather than MH) assumes that the string "nmh" will
be in mh-lib-progs or mh-lib.
At on Debian systems, nmh files are installed under
/usr/lib/mh/ so this check fails. Perhaps we should
check for something else?
There are several files found on one and not the other
that we could test for.
Peter
Logged In: YES
user_id=93690
Right. How about:
(setq mh-nmh-p (file-exists-p (concat mh-progs "/"
"mhbuild")))
? Alternates include mhshow and mhstore, but mhbuild feels
more primordial to me.
Logged In: YES
user_id=31877
> Right. How about:
>
> (setq mh-nmh-p (file-exists-p (concat mh-progs "/"
"mhbuild")))
Considering I was going to use mh-nmh-p to determine whether
to use mhbuild or not, this is an excellent choice!
Peter
Logged In: YES
user_id=31877
Closed in CVS version.
Peter