unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 20202@debbugs.gnu.org, phillip.lord@russet.org.uk,
	20484@debbugs.gnu.org, monnier@iro.umontreal.ca,
	emacs-devel@gnu.org
Subject: bug#20484: EMACS=t Joy and Happiness
Date: Fri, 25 May 2018 09:16:16 +0300	[thread overview]
Message-ID: <83sh6g9s5r.fsf__32883.6818262518$1527228968$gmane$org@gnu.org> (raw)
In-Reply-To: <6443412a-5803-d9c0-1ef3-ece7f49c43e1@cs.ucla.edu> (message from Paul Eggert on Thu, 24 May 2018 15:03:56 -0700)

> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Thu, 24 May 2018 15:03:56 -0700
> Cc: 20202@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
> 	20484@debbugs.gnu.org
> 
> Bash 4.4 came out only in September 2016, and it's too soon to assume 
> it.

I agree, 1.5 years is too soon.  I think we need 5 years at least.

> 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.

The first part will only work if Emacs is used on the same system
where it is built, right?  Is that a good assumption, given all the
binary distributions?





  parent reply	other threads:[~2018-05-25  6:16 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87tvqw4w8s.fsf@russet.org.uk>
2018-05-24 20:52 ` bug#20202: EMACS=t Joy and Happiness Stefan Monnier
2018-05-24 22:03 ` bug#20484: " Paul Eggert
2018-05-24 22:03 ` bug#20202: " Paul Eggert
     [not found] ` <6443412a-5803-d9c0-1ef3-ece7f49c43e1@cs.ucla.edu>
2018-05-25  2:25   ` Van L
2018-05-25  6:11     ` Ricardo Wurmus
2018-05-25  6:11     ` bug#20484: " Ricardo Wurmus
2018-05-25 17:59     ` bug#20202: " Paul Eggert
2018-05-25 17:59     ` bug#20484: " Paul Eggert
2018-05-25  6:16   ` bug#20202: " Eli Zaretskii
2018-05-25  6:16   ` Eli Zaretskii [this message]
     [not found]   ` <83sh6g9s5r.fsf@gnu.org>
2018-05-25  7:28     ` Van L
2018-05-25  7:28     ` bug#20484: " Van L
     [not found]     ` <ACB7DB0F-7E7E-405C-8F23-1B05F85E2134@scratch.space>
2018-05-25  8:02       ` bug#20202: " Eli Zaretskii
2018-05-25  8:02       ` bug#20484: " Eli Zaretskii
2018-05-25 22:34   ` Phillip Lord
2018-05-25 20:36 ` bug#20202: " Paul Eggert
2018-05-25 20:36 ` bug#20484: " Paul Eggert
     [not found] ` <85133880-5ae1-223a-50e6-4646adbf8052@cs.ucla.edu>
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     ` bug#20202: " Paul Eggert
     [not found]     ` <e81387b2-4135-573c-c839-cf0972bfd56c@cs.ucla.edu>
2018-05-31 21:07       ` Phillip Lord
2018-05-31 23:45         ` bug#20484: " Paul Eggert
2018-05-31 23:45         ` bug#20202: " Paul Eggert
     [not found]         ` <4ce6b85e-d600-872d-2a78-d9203d8c8259@cs.ucla.edu>
2018-06-01  1:56           ` 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
     [not found]           ` <836033gf7d.fsf@gnu.org>
2018-06-01 14:08             ` bug#20484: " Paul Eggert
2018-06-01 14:08             ` bug#20202: " Paul Eggert
     [not found]             ` <9010057b-aa05-9074-49f1-aeab26cfc7cb@cs.ucla.edu>
2018-06-01 14:14               ` bug#20484: " Eli Zaretskii
2018-06-14 20:54                 ` bug#20202: " Paul Eggert
2018-06-14 20:54                 ` 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

  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='83sh6g9s5r.fsf__32883.6818262518$1527228968$gmane$org@gnu.org' \
    --to=eliz@gnu.org \
    --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 \
    --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).