unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: So clever it's stupid
Date: Tue, 14 Oct 2008 07:09:58 -0600	[thread overview]
Message-ID: <gd25n1$nng$1@ger.gmane.org> (raw)
In-Reply-To: <87tzbfqw9h.fsf@nonospaz.fatphil.org>

Phil Carmody wrote:
> How do I turn off the utterly obnoxious behaviour of '<' in shell mode?
> (Emacs v.21.4.1)
> 
> <<<
> sh-maybe-here-document is an interactive compiled Lisp function in `sh-script'.
> (sh-maybe-here-document ARG)
> 
> Insert self.  Without prefix, following unquoted `<' inserts here document.
> The document is bounded by `sh-here-document-word'.
> 
> I give all my heredocs meaningful individual names, and certainly don't want 
> emacs inanely thinking that I want all the terminators called 'EOF'.
> 
> It's so completely brain-dead that if I try to type a command like
>   echo '<<< doing phase 2 >>>'
> I don't get past the second chevron before it's shat unwanted garbage
> in my file.
> 
> Similarly it doesn't seem to understand that people might want to use
> both expanded and non-expanded heredocs, or sometimes want leading
> tab removal, but at other times not want it. And as for herestrings,
> they're right out.
> 
> Magic '<', for me, must die. How do I ensure I never ever see that
> abomination again? (Unbind the key and make it self-insert in a 
> bunch of relevant hooks? Or is there just a variable I can set to 
> 'off' somehow?)

The former:

(add-hook 'sh-mode-hook (lambda () (local-unset-key "<")))

-- 
Kevin Rodgers
Denver, Colorado, USA





  reply	other threads:[~2008-10-14 13:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14 10:57 So clever it's stupid Phil Carmody
2008-10-14 13:09 ` Kevin Rodgers [this message]
     [not found] ` <mailman.1007.1223989809.25473.help-gnu-emacs@gnu.org>
2008-10-14 13:21   ` Phil Carmody
2008-10-14 18:25 ` Xavier Maillard

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='gd25n1$nng$1@ger.gmane.org' \
    --to=kevin.d.rodgers@gmail.com \
    --cc=help-gnu-emacs@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.
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).