all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: Emacs-Devel devel <emacs-devel@gnu.org>
Cc: 20202@debbugs.gnu.org, Paul Eggert <eggert@cs.ucla.edu>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	20484@debbugs.gnu.org
Subject: EMACS=t Joy and Happiness
Date: Thu, 24 May 2018 21:46:59 +0100	[thread overview]
Message-ID: <87tvqw4w8s.fsf@russet.org.uk> (raw)



Well, it hardly seems like Mon, 11 Apr 2016 since last we discussed this
issue.

If you remember, we managed to blitz, EMACS=t everywhere, then Paul
restored it in term.el because it broke bash otherwise. master currently
looks like this:

  ;; This is for backwards compatibility with Bash 4.3 and earlier.
  ;; Remove this hack once Bash 4.4-or-later is common, because
  ;; it breaks './configure' of some packages that expect it to
  ;; say where to find EMACS.
  (format "EMACS=%s (term:%s)" emacs-version term-protocol-version)

I worry that "Bash 4.4 or later is common" is rather indeterminate; my
desktop is now 4.4.19. but another machine I am using has bash
4.2.46. Given that Emacs-26 is now destined to come out with
EMACS=26.1.0, I would like to propose that we now remove this on master,
i.e. make it happen for Emacs-27 which should be in about 2020.

Phil







             reply	other threads:[~2018-05-24 20:46 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-24 20:46 Phillip Lord [this message]
2018-05-24 20:52 ` EMACS=t Joy and Happiness Stefan Monnier
2018-05-24 20:52 ` bug#20202: " Stefan Monnier
2018-05-24 22:03 ` Paul Eggert
2018-05-24 22:03 ` bug#20484: " Paul Eggert
2018-05-24 22:03 ` Paul Eggert
2018-05-25  2:25   ` bug#20202: " Van L
2018-05-25  6:11     ` Ricardo Wurmus
2018-05-25  6:11     ` bug#20484: " Ricardo Wurmus
2018-05-25  6:11     ` Ricardo Wurmus
2018-05-25  7:12       ` Van L
2018-05-25 17:59     ` bug#20202: " Paul Eggert
2018-05-25 17:59     ` bug#20484: " Paul Eggert
2018-05-25 17:59     ` Paul Eggert
2018-05-26  0:17       ` Van L
2018-05-26  7:41         ` Eli Zaretskii
2018-05-26 10:07           ` Van L
2018-05-26 10:57             ` Eli Zaretskii
2018-05-26  0:43       ` Van L
2018-05-25  6:16   ` bug#20484: " Eli Zaretskii
2018-05-25  6:16   ` bug#20202: " Eli Zaretskii
2018-05-25  6:16   ` Eli Zaretskii
2018-05-25  7:28     ` bug#20484: " Van L
2018-05-25  7:28     ` bug#20202: " Van L
2018-05-25  7:28     ` Van L
2018-05-25  8:02       ` bug#20202: " Eli Zaretskii
2018-05-25  8:02       ` Eli Zaretskii
2018-05-26  0:01         ` Van L
2018-05-25  8:02       ` bug#20484: " Eli Zaretskii
2018-05-25 17:50     ` Paul Eggert
2018-05-25 22:34   ` bug#20484: " Phillip Lord
2018-05-25 20:36 ` Paul Eggert
2018-05-25 22:49   ` bug#20202: " Phillip Lord
2018-05-26  7:20   ` bug#20484: " Eli Zaretskii
2018-05-26 20:54     ` Paul Eggert
2018-05-31 21:07       ` bug#20202: " Phillip Lord
2018-05-31 23:45         ` Paul Eggert
2018-06-01  1:56           ` Stefan Monnier
2018-06-01  1:56           ` bug#20202: " Stefan Monnier
2018-06-01  1:56           ` bug#20484: " Stefan Monnier
2018-06-01  7:04           ` Eli Zaretskii
2018-06-01 14:08             ` bug#20202: " Paul Eggert
2018-06-01 14:08             ` bug#20484: " Paul Eggert
2018-06-01 14:08             ` Paul Eggert
2018-06-01 14:14               ` bug#20484: " Eli Zaretskii
2018-06-14 20:54                 ` bug#20202: " Paul Eggert
2018-06-14 20:54                 ` Paul Eggert
2018-06-14 20:54                 ` bug#20484: " Paul Eggert
2018-06-01  7:04           ` Eli Zaretskii
2018-06-01  7:04           ` bug#20202: " Eli Zaretskii
2018-05-31 23:45         ` bug#20484: " Paul Eggert
2018-05-31 23:45         ` bug#20202: " Paul Eggert
2018-05-26 20:54     ` bug#20484: " Paul Eggert
2018-05-26 20:54     ` bug#20202: " Paul Eggert
2018-05-25 20:36 ` bug#20484: " Paul Eggert
2018-05-25 20:36 ` bug#20202: " Paul Eggert

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=87tvqw4w8s.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=20202@debbugs.gnu.org \
    --cc=20484@debbugs.gnu.org \
    --cc=eggert@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 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.