unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Phillip Lord" <phillip.lord@russet.org.uk>
Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: Considered Harmful 73d213: 'Comint, term, and compile new set Emacs'
Date: Thu, 07 Apr 2016 18:07:45 +0300	[thread overview]
Message-ID: <83lh4plany.fsf@gnu.org> (raw)
In-Reply-To: <c32b8d04f5c78203f06c4e48e03b37b0.squirrel@cloud103.planethippo.com> (phillip.lord@russet.org.uk)

> Date: Thu, 7 Apr 2016 08:35:23 +0100
> From: "Phillip Lord" <phillip.lord@russet.org.uk>
> Cc: emacs-devel@gnu.org, eggert@penguin.cs.ucla.edu, monnier@iro.umontreal.ca,
> 	Phillip Lord <phillip.lord@russet.org.uk>
> 
> As a better alternatively, would it be possible to find a solution to
> 20484 which does not involve EMACS=t?
> 
> This would both address 20484 and 20202, rather than robbing Peter to pay
> Paul.

Bug#20484 is with a version of Bash that needs $EMACS to be set,
right?  If so, how can we solve it, if the changes to do that must be
made in Bash?



  reply	other threads:[~2016-04-07 15:07 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
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 [this message]
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=83lh4plany.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --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).