From:	stodghil AT cs DOT cornell DOT edu (Paul Stodghill)
Subject:	[Solved!] Re: [Workaround] Re: M-x shell + bash = Infinite error messages?
17 Dec 1997 16:53:27 -0800 :
Message-ID:	<mlu3c7vcs2.fsf.cygnus.gnu-win32@mario.cs.cornell.edu>
References:	<199712171141 DOT LAA29386 AT shirow DOT long DOT harlequin DOT co DOT uk>
Mime-Version:	1.0 (generated by tm-edit 7.106)
To:	ntemacs-users AT cs DOT washington DOT edu
Cc:	gnu-win32 AT cygnus DOT com

Andrew Innes said:
> On 16 Dec 1997 13:44:45 -0500, Paul Stodghill <stodghil AT CS DOT Cornell DOT EDU> said:
> >I figured out what was causing my problem:
> 
> [problem was bash crashing when run in an Emacs shell buffer]
> 
> >I was invoking emacs by using a command similar to,
> >
> >  bash -c "runemacs ... some options ..."
> >
> >Changing the command to simply
> >
> >  runemacs ... some options ...
> >
> >made by M-x shell problems go away.
> >
> >Why?
> 
> runemacs starts Emacs then exits, so possibly an environment variable is
> being set by bash which is passed on to Emacs, causing confusion later.

Bingo! The environment variable in question is PID. Setting PID (either by
using bash to invoke runemacs, or by M-x setenv) causes M-x shell to die a
horrible death.

Adding

	(setenv "PID" nil)

to my ~/.emacs fixes the problem.

Thanks for your help!

-- 
Paul Stodghill <stodghil AT cs DOT cornell DOT edu>
http://www.cs.cornell.edu/home/stodghil/home.html
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -