From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Bug in shell.el: explicit-bash-args does not work for bash 1.x
Date: 25 Oct 2002 16:28:00 +0200 [thread overview]
Message-ID: <5xn0p2mw3z.fsf@kfs2.cua.dk> (raw)
It is quite a mystery to me why I just started to get bitten by the
follow change [which is now 4 month old]:
2002-06-28 Andreas Schwab <schwab@suse.de>
* shell.el (explicit-bash-args): New user option.
This is specified to define explicit-bash-args to --noediting -i
which are the proper options for bash 2.x
However, for bash 1.x (included with e.g. redhat 6.2), the --noediting
option isn't recognized and bash refuses to start.
For bash 1.x, the corresponding option was named -nolineediting, but
even setting that option doesn't really work, as (for some reason I
don't understand) process-send-eof is then unable to terminate the
running bash 1.x (so C-d at EOB no longer exits the shell)!
Only reverting back to explicit-bash-args not including neither
--noediting nor -nolineediting makes it work ok.
As I said above, I'm puzzled why I didn't discover this earlier -- I
use shell buffers all the time, but maybe it's been some time since I
actually did that on the system where I still have redhat 6.2
installed.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next reply other threads:[~2002-10-25 14:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 14:28 Kim F. Storm [this message]
2002-10-26 20:13 ` Bug in shell.el: explicit-bash-args does not work for bash 1.x Richard Stallman
2002-10-27 0:17 ` Kim F. Storm
2002-10-28 19:19 ` Richard Stallman
2002-10-28 21:48 ` Stefan Monnier
2002-10-28 23:29 ` Kim F. Storm
2002-10-29 6:17 ` Eli Zaretskii
2002-10-29 6:15 ` Eli Zaretskii
2002-10-29 14:42 ` Stefan Monnier
2002-10-29 7:40 ` Kai Großjohann
2002-10-30 21:32 ` Kim F. Storm
2002-10-31 6:33 ` Kai Großjohann
2002-10-29 11:29 ` Richard Stallman
2002-11-01 0:38 ` Kim F. Storm
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=5xn0p2mw3z.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
/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).