🚀 go-pugleaf

Hi, I just got MH version 6.7.2 to upgrade from 6.4. Everything seems
to work fine, except when I try to use the Emacs interface.
Apparently, in this case, mh commands die from a SIGPIPE. The exact
command which causes this is (paraphrased from mh-exec-cmd-output):

(apply 'call-process "/usr/local/mh/bin/scan" nil t nil '("+inbox"))
"write on a pipe with no one to read it"

Has anyone seen anything like this before? If not, this is going to be
a pain to debug since it only seems to happen when run from
call-process. For you Emacs experts, what's the difference between
running the command as above, and using M-x shell-command? I'm running
on an NCR 3434 (i486) running System 5 Release 4. The relevant version
information follows. 

"GNU Emacs 18.58.3 of Tue Mar 24 1992 on riipsdev (usg-unix-v)"

version: MH 6.7.2 #14[UCI] (riipsdev) of Mon Jun 1 09:22:16 EDT 1992
options: [MHE] [MHRC] [MORE='"/usr/local/bin/less"'] [NOMHSEQ] [RPATHS]
         [SBACKUP='"#"'] [SENDMTS] [SHADOW] [SMTP] [SOCKETS] [SVR4]
         [SYS5] [SYS5DIR] [TYPESIG=void]

MH was compiled in the System V environment, not the Berkeley
environment as suggested in the sample config file. The comment in the
file that you must compile in the Berkeley environment to get sockets
is wrong, or at least out of date. I also tweaked it to use shared
libraries, and I'll send the diffs back as soon as I get this problem
fixed.

--
Tony Lill,                           ajlill@riipsdev.Waterloo.NCR.COM
President, A. J. Lill Consultants                 (519) 650 0660
539 Grand Valley Dr., Cambridge, Ont.             (519) 653 9732
presently at E&M Waterloo, NCR Canada Ltd.        (519) 884 1710 x624
					     voice plus 643 1624

"Welcome to All Things UNIX, where if it's not UNIX, it's CRAP!"