unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: Paul Eggert <eggert@cs.ucla.edu>
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, 05 Apr 2016 17:38:11 +0100	[thread overview]
Message-ID: <87k2kcovt8.fsf@russet.org.uk> (raw)
In-Reply-To: <5703E15B.7080601@cs.ucla.edu> (Paul Eggert's message of "Tue, 5 Apr 2016 09:01:31 -0700")

Paul Eggert <eggert@cs.ucla.edu> writes:

> On 04/05/2016 04:05 AM, Phillip Lord wrote:
>> Not sure how to fix this, but the commentary prior to commit beaab89
>> says "we are going to rid of this binding, probably in Emacs 23". It
>> seems a shame to be three major versions wrong.
> Yes, this change has been frustrating to implement (see Bug#20484), because we
> need to wait until the new Bash is released and more widely available, as
> current Bash is incompatible with the change.

I understand the problem, and did read the bug report.


> It sounds like you have a workaround in mind for cask and ert-runner. Is there
> some problem in installing the workaround? Presumably they need to work in
> older Emacs anyway, so they already have a way to deal with this issue.

Well, it doesn't work now. Cask used to just ditch $EMACS. Now it checks
the value of INSIDE_EMACS and does one thing in Emacs-24 (ditches
$EMACS) and another in Emacs-25 (uses $EMACS). In other words, I don't
have a workaround, I have limited the scope of the existing workaround
to Emacs-24. All of this semantics will now have to be backed out, since
it is all wrong.

The only saving grace is that I added $CASK_EMACS at the same time,
which avoids the name clash entirely. But this also needs to be
percolated to downstream tools like ert-runner.

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.

Phil





  reply	other threads:[~2016-04-05 16:38 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 [this message]
2016-04-05 20:42     ` Paul Eggert
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=87k2kcovt8.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=eggert@cs.ucla.edu \
    --cc=eggert@penguin.cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).