From: Paul Eggert <eggert@cs.ucla.edu>
To: Phillip Lord <phillip.lord@russet.org.uk>
Cc: eggert@penguin.cs.ucla.edu, monnier@iro.umontreal.ca,
emacs-devel@gnu.org
Subject: Re: Considered Harmful 73d213: "Comint, term, and compile new set Emacs"
Date: Tue, 5 Apr 2016 13:42:35 -0700 [thread overview]
Message-ID: <5704233B.4020103@cs.ucla.edu> (raw)
In-Reply-To: <87k2kcovt8.fsf@russet.org.uk>
On 04/05/2016 09:38 AM, Phillip Lord wrote:
> I don't
> have a workaround, I have limited the scope of the existing workaround
> to Emacs-24.
Would something like the following be an adequate workaround? The idea
is to have code that works with both Emacs 25 and Emacs 24 (and Emacs 23
etc., for that matter):
def get_emacs_from_env():
emacs = ENVB.get(b'CASK_EMACS')
if emacs:
return emacs
emacs = ENVB.get(b'EMACS')
if emacs != 't':
return emacs
return None
> Is there not a different solution to the bash problem? Passing
> --noediting as an option would work, I think, and it should work with
> both the old and new $EMACS handling of bash.
>
Part of the worry here is that programs other than Bash will be
affected, and that we need to give people some time to adjust to the
changed behavior of Emacs, by announcing the planned change in Emacs 25
and then actually making the change in a later Emacs release.
next prev parent reply other threads:[~2016-04-05 20:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 11:05 Considered Harmful 73d213: "Comint, term, and compile new set Emacs" Phillip Lord
2016-04-05 16:01 ` Paul Eggert
2016-04-05 16:38 ` Phillip Lord
2016-04-05 20:42 ` Paul Eggert [this message]
2016-04-05 22:08 ` Phillip Lord
2016-04-06 0:25 ` Paul Eggert
2016-04-06 17:53 ` Phillip Lord
2016-04-07 1:05 ` Paul Eggert
2016-04-07 7:18 ` Considered Harmful 73d213: 'Comint, term, and compile new set Emacs' Phillip Lord
2016-04-07 7:35 ` Phillip Lord
2016-04-07 15:07 ` Eli Zaretskii
2016-04-07 15:21 ` Phillip Lord
2016-04-07 15:26 ` 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=5704233B.4020103@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=eggert@penguin.cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--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).