From: Chet Ramey <chet.ramey@case.edu>
Cc: bug-gnu-emacs@gnu.org, gnuplot-bugs@lists.sourceforge.net,
bug-autoconf@gnu.org, Don.Bashford@stjude.org,
chet.ramey@case.edu
Subject: Re: emacs Shell mode vs AC_CHECK_PROG(EMACS, ...)
Date: Mon, 11 Sep 2006 16:55:09 -0400 [thread overview]
Message-ID: <060911205509.AA17674.SM@caleb.ins.cwru.edu> (raw)
In-Reply-To: Message from rms@gnu.org of Mon, 11 Sep 2006 15:57:59 -0400 (id <E1GMrup-0007rl-9m@fencepost.gnu.org>)
> For a short-term correction, I think the easiest way is to change
> Autoconf to ignore a value of `t' for this environment variable.
> Autoconf maintainers, what do you think?
>
> For longer term, perhaps the best thing is to change Emacs to use a
> different environment variable. Alas, I don't remember what software
> checks that environment variable, or the motive for binding it.
>
> Is it Bash? I have cc'd the Bash maintainer so he can answer.
Bash does inspect the EMACS environment variable as part of checking
whether or not to turn off line editing even when the shell is
interactive. It also checks for TERM==emacs. If the shell discovers
it's running in an emacs buffer, it turns off readline.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
Live Strong.
Chet Ramey, ITS, CWRU chet@case.edu http://tiswww.tis.case.edu/~chet/
next prev parent reply other threads:[~2006-09-11 20:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 3:46 emacs Shell mode vs AC_CHECK_PROG(EMACS, ...) Don.Bashford
2006-09-11 17:42 ` Paul Eggert
2006-09-12 15:28 ` Richard Stallman
2006-09-11 19:57 ` Richard Stallman
2006-09-11 20:55 ` Chet Ramey [this message]
2006-09-11 21:40 ` Don.Bashford
2006-09-11 21:10 ` Don.Bashford
[not found] ` <mailman.6803.1158013410.9609.bug-gnu-emacs@gnu.org>
2006-09-13 13:58 ` Miles Bader
2006-09-13 17:12 ` Chet Ramey
2006-09-13 22:10 ` Kim F. Storm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=060911205509.AA17674.SM@caleb.ins.cwru.edu \
--to=chet.ramey@case.edu \
--cc=Don.Bashford@stjude.org \
--cc=bug-autoconf@gnu.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=gnuplot-bugs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.