Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!samsung!caesar.cs.montana.edu!ogccse!reed!trost
From: trost@reed.bitnet (Bill Trost)
Newsgroups: gnu.bash.bug
Subject: Re: file completion doing ugly things under xterm
Message-ID: <13643@reed.UUCP>
Date: 30 Nov 89 01:01:49 GMT
References: <13591@reed.UUCP> <8911170723.AA09412@aurel.cns.caltech.edu.>
	<13593@reed.UUCP> <KHAI.89Nov22101859@babar.amara.uucp>
Sender: news@reed.UUCP
Lines: 15

>It turns out that when you invoke bash, the variable "EMACS" must
>*not* be set.  If it is, bash thinks that it is running within Emacs
>or something and does wierd things, the bad file completion being one
>result.

Bleah; yeah, I found the getenv("EMACS") in readline.c.  Might I
suggest that the check be made for TERM being set to emacs, instead of
the variable EMACS being checked, for those of us who start up xterms
from emacs?  (Seems like a saner way to do the check, anyhow)

And, on the other side of the coin, if it is determined that we are
running under emacs, bash shouldn't give you back the command line to
edit when a history lookup fails (eg, !sp instead of !ps).
--
--