From: Glenn Morris <rgm@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Phillip Lord <phillip.lord@russet.org.uk>,
20202@debbugs.gnu.org, monnier@iro.umontreal.ca,
20484@debbugs.gnu.org
Subject: bug#20202: Considered Harmful 73d213: 'Comint, term, and compile new set Emacs'
Date: Thu, 07 Apr 2016 12:01:05 -0400 [thread overview]
Message-ID: <jia8l576im.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <57067BF6.6000700@cs.ucla.edu> (Paul Eggert's message of "Thu, 7 Apr 2016 08:25:42 -0700")
Paul Eggert wrote:
> On 04/07/2016 08:18 AM, Phillip Lord wrote:
>> I can think of several possibilities. In particular, the EMACS=t behaviour
>> of bash should also be replicable with bash -o emacs.
> I expect that this problem affects programs other than bash. For
> example, tcsh 6.19.00 (the latest version of the first other shell
> that I checked) tests whether EMACS is "t".
IMO this issue is effectively going to be impossible to change.
Eg is there any sign of tcsh adapting?
How long for that change to make it into the long-term stable release of
all major distributions?
How many other things need similar changes?
Just resign yourself to the fact that EMACS has a not-very useful value
inside comint.
next prev parent reply other threads:[~2016-04-07 16:01 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87oa9otixb.fsf@russet.org.uk>
[not found] ` <5703E15B.7080601@cs.ucla.edu>
[not found] ` <87k2kcovt8.fsf@russet.org.uk>
[not found] ` <5704233B.4020103@cs.ucla.edu>
[not found] ` <8737qzso88.fsf@russet.org.uk>
[not found] ` <57045765.4000309@cs.ucla.edu>
[not found] ` <87r3ei8vz9.fsf@russet.org.uk>
[not found] ` <5705B246.10201@cs.ucla.edu>
[not found] ` <74bf15b3e1a5afeb41cf6b39d5247e8b.squirrel@cloud103.planethippo.com>
2016-04-07 14:57 ` bug#20202: Considered Harmful 73d213: 'Comint, term, and compile new set Emacs' Paul Eggert
[not found] ` <c32b8d04f5c78203f06c4e48e03b37b0.squirrel@cloud103.planethippo.com>
2016-04-07 15:01 ` Paul Eggert
2016-04-07 15:18 ` Phillip Lord
2016-04-07 15:25 ` Paul Eggert
2016-04-07 16:01 ` Glenn Morris [this message]
2016-04-07 16:07 ` Phillip Lord
2016-04-07 16:26 ` bug#20484: " Paul Eggert
2016-04-07 19:55 ` Phillip Lord
2016-04-07 22:20 ` bug#20484: " Stefan Monnier
2016-04-08 7:05 ` Eli Zaretskii
2016-04-08 13:09 ` Phillip Lord
2016-04-08 20:50 ` Paul Eggert
2016-04-08 21:20 ` Phillip Lord
2016-04-08 7:03 ` bug#20484: " Eli Zaretskii
2016-04-08 7:34 ` Andreas Schwab
2016-04-08 13:12 ` bug#20484: " Phillip Lord
2016-04-07 21:42 ` Phillip Lord
2016-04-08 7:01 ` Eli Zaretskii
2016-04-08 16:49 ` bug#20202: " Stefan Monnier
2016-04-08 18:12 ` Phillip Lord
2016-04-07 16:51 ` Stefan Monnier
2016-04-07 16:59 ` bug#20202: " Eli Zaretskii
2016-04-07 18:58 ` Stefan Monnier
2016-04-07 19:25 ` Eli Zaretskii
2016-04-07 22:01 ` Stefan Monnier
2016-04-08 7:00 ` bug#20202: " Eli Zaretskii
2016-04-08 15:32 ` Glenn Morris
2016-04-08 15:59 ` Eli Zaretskii
2015-05-01 23:36 ` bug#20484: 25.0.50; Directory tracking in ansi-term broken Jacob Oursland
2015-05-02 2:17 ` Glenn Morris
2015-05-02 2:43 ` Glenn Morris
2015-05-02 19:33 ` Jacob Oursland
2015-05-03 5:45 ` Stefan Monnier
2015-05-03 6:15 ` Jacob Oursland
2015-05-03 16:29 ` Richard Stallman
2015-05-03 17:36 ` Jacob Oursland
2015-05-04 2:06 ` Stefan Monnier
2015-05-04 16:15 ` Richard Stallman
2015-05-03 17:57 ` Glenn Morris
2015-05-03 19:09 ` Jacob Oursland
2015-05-04 2:07 ` Stefan Monnier
2016-03-23 22:15 ` Paul Eggert
2016-04-08 18:47 ` bug#20484: Bash 4.4-rc1 incompatibility with future Emacs $EMACS Paul Eggert
2016-04-09 2:24 ` bug#20484: bug#20202: Considered Harmful 73d213: 'Comint, term, and compile new set Emacs' Glenn Morris
2016-04-09 8:43 ` Phillip Lord
2016-04-09 13:43 ` bug#20202: " Stefan Monnier
2016-04-09 21:56 ` Phillip Lord
2016-04-09 23:40 ` bug#20202: " Paul Eggert
2016-04-10 0:08 ` Stefan Monnier
2016-04-10 3:30 ` Paul Eggert
2016-04-10 13:57 ` Stefan Monnier
2016-04-11 5:50 ` bug#20202: " Paul Eggert
2016-04-10 8:26 ` bug#20484: " Phillip Lord
2016-04-10 13:59 ` Stefan Monnier
2016-04-11 12:32 ` bug#20484: " Phillip Lord
2016-04-10 8:25 ` Phillip Lord
2015-03-25 21:44 ` bug#20202: 24.3; Comint mode sets a bad $EMACS Eli Barzilay
2015-03-26 0:46 ` Stefan Monnier
2015-03-28 15:27 ` Eli Barzilay
2015-04-09 15:02 ` Stefan Monnier
2016-04-10 12:18 ` bug#20202: bug#20484: bug#20202: Considered Harmful 73d213: 'Comint, term, and compile new set Emacs' Markus Triska
2016-04-11 12:38 ` Phillip Lord
2018-05-24 20:46 ` bug#20202: EMACS=t Joy and Happiness Phillip Lord
2016-04-10 7:13 ` bug#20202: bug#20484: bug#20202: Considered Harmful 73d213: 'Comint, term, and compile new set Emacs' Michael Albinus
2016-04-10 8:51 ` Phillip Lord
2016-04-10 9:31 ` Michael Albinus
2016-04-08 16:46 ` Stefan Monnier
2016-04-08 17:12 ` Paul Eggert
2016-04-08 18:14 ` bug#20202: " Phillip Lord
2016-04-08 17:47 ` Phillip Lord
2016-04-08 13:15 ` Phillip Lord
2016-04-08 13:40 ` Eli Zaretskii
2016-04-08 15:45 ` bug#20202: " Glenn Morris
2016-04-08 16:01 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jia8l576im.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=20202@debbugs.gnu.org \
--cc=20484@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=monnier@iro.umontreal.ca \
--cc=phillip.lord@russet.org.uk \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).