🚀 go-pugleaf

Sorry for posting, but even uunet doesn't seem to know how to
deliver to teradyne.  (Just what is one supposed to do with
host.UUCP from the Internet?).

In anycase the answer _may_ be of use to others...

In <9106172352.AA02361@midas.teradyne.uucp> rogoff@teradyne.UUCP (David Rogoff) writes:
>I've run into this problem in two programs.  Both let you specify
>a default editor (setenv EDITOR gnuemacs).  Both programs invoke the
>editor with the command:
>    sh -c gnuemacs /tmp/xxxxx
>This just hangs until the process is killed.  What does gnuemacs
>have against Bourne shells?

I reported this as a bug against /bin/sh on our sun386i's ages
ago...
During its initalization, emacs does some fiddling with job
control stuff.  It is this that stuff's /bin/sh a ps -axl will
probably show the process is stopped 'T'.

>We are running 18.53.2 on SparcStation 1 with SunOS 4.1.

Fortunately the initialization code in emacs-18.55 is slightly
different and does work with /bin/sh.
Interestingly we _never_ had this problem on Sun-3's.

So, you can:
1/ use csh for now,
2/ upgrade emacs to 18.55 or later.
3/ remind Sun that that problem persists.

Sorry, I never had time to explore _exactly_ what was going
wrong...
-- 
Simon J. Gerraty		<sjg@melb.bull.oz.au>

#include <disclaimer,_witty_comment>