From: phillip.lord@russet.org.uk (Phillip Lord)
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Emacs-Devel devel <emacs-devel@gnu.org>,
20484@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
20202@debbugs.gnu.org
Subject: bug#20484: EMACS=t Joy and Happiness
Date: Fri, 25 May 2018 23:34:20 +0100 [thread overview]
Message-ID: <87k1rrl5zn.fsf@russet.org.uk> (raw)
In-Reply-To: <6443412a-5803-d9c0-1ef3-ece7f49c43e1@cs.ucla.edu> (Paul Eggert's message of "Thu, 24 May 2018 15:03:56 -0700")
Paul Eggert <eggert@cs.ucla.edu> writes:
> Bash 4.4 came out only in September 2016, and it's too soon to assume
> it. For example, my students regularly use Emacs on a server running
> RHEL 7, which ships Bash 4.2.46, and as I understand it, this is the
> most recent RHEL available.
Well, Emacs-27 will come out in 2020, so that's 4 years lead time. And
the most recent of RHEL also ships with Emacs-24. So, by the time RHEL
ships Emacs-27, good chance it will ship Bash 4.4.
> How about this idea: At Emacs build time, we check whether Bash is 4.4
> or later, and if so we use a term.el that assumes bash 4.4 or
> later. Otherwise, we use a term.el that interrogates the shell
> dynamically for whether it is shell and if so what its version number
> is, the first time that Emacs runs a process under a shell.
Well, the latter half we could do (I don't think the build idea makes
sense). But I was hoping to make life simpler, not more complex.
Phil
next prev parent reply other threads:[~2018-05-25 22:34 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 20:46 EMACS=t Joy and Happiness Phillip Lord
2018-05-24 20:52 ` bug#20202: " Stefan Monnier
2018-05-24 20:52 ` Stefan Monnier
2018-05-24 22:03 ` bug#20202: " 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 7:12 ` Van L
2018-05-25 6:11 ` bug#20484: " Ricardo Wurmus
2018-05-25 6:11 ` bug#20202: " Ricardo Wurmus
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 17:59 ` bug#20484: " Paul Eggert
2018-05-25 17:59 ` bug#20202: " Paul Eggert
2018-05-25 6:16 ` bug#20484: " Eli Zaretskii
2018-05-25 6:16 ` Eli Zaretskii
2018-05-25 7:28 ` bug#20202: " Van L
2018-05-25 7:28 ` Van L
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 8:02 ` bug#20202: " Eli Zaretskii
2018-05-25 7:28 ` bug#20484: " Van L
2018-05-25 17:50 ` Paul Eggert
2018-05-25 6:16 ` bug#20202: " Eli Zaretskii
2018-05-25 22:34 ` Phillip Lord [this message]
2018-05-24 22:03 ` bug#20484: " Paul Eggert
2018-05-25 20:36 ` bug#20202: " Paul Eggert
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-26 20:54 ` Paul Eggert
2018-05-31 21:07 ` bug#20202: " Phillip Lord
2018-05-31 23:45 ` Paul Eggert
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 7:04 ` bug#20202: " Eli Zaretskii
2018-06-01 7:04 ` Eli Zaretskii
2018-06-01 14:08 ` Paul Eggert
2018-06-01 14:14 ` bug#20484: " Eli Zaretskii
2018-06-14 20:54 ` Paul Eggert
2018-06-14 20:54 ` bug#20484: " Paul Eggert
2018-06-14 20:54 ` bug#20202: " Paul Eggert
2018-06-01 14:08 ` bug#20484: " Paul Eggert
2018-06-01 14:08 ` bug#20202: " Paul Eggert
2018-05-31 23:45 ` bug#20484: " Paul Eggert
2018-05-26 20:54 ` bug#20202: " Paul Eggert
2018-05-25 20:36 ` bug#20484: " 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=87k1rrl5zn.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.