[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: EMACS=t causes problems
From: |
Chet Ramey |
Subject: |
Re: EMACS=t causes problems |
Date: |
Tue, 11 Nov 2003 09:52:05 -0500 |
> Bash 2.05b turns off line editing provided by readline/history if it
> detects the environment variable "EMACS" has the value "t". That
> variable is set in a shell running in an emacs shell buffer. The
> problem is that it is inherited by every process started there. If I
> start xterm from such a shell buffer, than command line editing is
> mysteriously broken.
The original request came from Richard Stallman; reproduced below. If
you want to debate its necessity, please take it up with him.
Chet
Date: Mon, 1 Jul 2002 08:09:45 -0600 (MDT)
Message-Id: <200207011409.g61E9jT07759@aztec.santafe.edu>
From: Richard Stallman <rms@gnu.org>
To: chet@po.cwru.edu
Subject: Turning off Readline
Emacs used to set TERM=emacs to tell subshells that they are
running under Emacs. Bash responds by turning off Readline.
With Terminfo, using TERM=emacs does not work, so Emacs does not do
it. So Bash fails to turn off Readline. However, Emacs also defines
EMACS=t. Could you make Bash check for that, too?
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
Live...Laugh...Love
Chet Ramey, ITS, CWRU chet@po.cwru.edu http://tiswww.tis.cwru.edu/~chet/