unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Jacobson <jidanni@dman.ddts.net>
Subject: Re: no pangs of guilt that can't turn off M-x shell's ^ ! ?
Date: Wed, 19 Mar 2003 14:52:55 +0800	[thread overview]
Message-ID: <87he9zu9tk.fsf@jidanni.org> (raw)
In-Reply-To: 3E77503D.90302@ihs.com

>> The shell-mode author thought csh-style ! and ^ history
>> substitutions were so great, he forgot to leave a way to turn them off.

K> C-h v comint-input-autoexpand

K> Does setting that variable to nil in a shell-mod-hook function fix your problem?

Hmm, I already had
(add-hook 'comint-mode-hook
  (function (lambda ()(setq comint-input-autoexpand nil)))) ;no more "!" surprizes
OK, now I will add
(add-hook 'shell-mode-hook
  (function (lambda ()(setq comint-input-autoexpand nil)))) ;no more "!" surprizes
for double protection. Thanks.

Blame
-----
Blame for my troubles can be conveniently shifted onto the Info page for saying

      Shell mode can optionally expand history references in the buffer
   when you send them to the shell.  To request this, set the variable
   `comint-input-autoexpand' to `input'.  You can make <SPC> perform
   history expansion by binding <SPC> to the command `comint-magic-space'.

It said 'optionally' when indeed it is doing it somewhat already by default.

Odd, in the source it says
(defcustom comint-input-autoexpand nil
But when I do
$ LC_ALL=C emacs --no-site-file -q -nw -f shell
and check its value, it is 'history.
Yes, I wish it was history, as in out of here :-)

  reply	other threads:[~2003-03-19  6:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3247.1047784613.21513.bug-gnu-emacs@gnu.org>
2003-03-17 16:39 ` no pangs of guilt that can't turn off M-x shell's ^ ! ? Kevin Rodgers
2003-03-18  0:09   ` Dan Jacobson
     [not found]   ` <mailman.3309.1047964346.21513.bug-gnu-emacs@gnu.org>
2003-03-18 16:58     ` Kevin Rodgers
2003-03-19  6:52       ` Dan Jacobson [this message]
2003-03-15 18:55 Dan Jacobson

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=87he9zu9tk.fsf@jidanni.org \
    --to=jidanni@dman.ddts.net \
    /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).