From: Eli Zaretskii <eliz@gnu.org>
To: thibaut.verron@gmail.com
Cc: emacs-devel@gnu.org
Subject: Re: Default setting for sh-maybe-here-document-mode
Date: Fri, 20 Feb 2015 10:31:54 +0200 [thread overview]
Message-ID: <83r3tlkmpx.fsf@gnu.org> (raw)
In-Reply-To: <CAFsi02T1WV7_c668M=pwsBysAr1EvPzwJZs819fBFQ9PB2RbOg@mail.gmail.com>
> From: Thibaut Verron <thibaut.verron@gmail.com>
> Date: Fri, 20 Feb 2015 09:19:22 +0100
>
> I was wondering why is `sh-electric-here-document-mode` activated by default
> for new documents in `sh-mode`? In my opinion, it is confusing to beginners,
> and working around it is difficult.
>
> I was under the impression that in most cases, this kind of commands, inserting
> text beyond what the user types, without requiring anything besides text input,
> are disabled by default. AUCTeX's electric backslash, for example, require a
> specific option to be set, even though in most cases it can be transparent
> input-wise (just visually confusing). Another example is dabbrev, which needs
> to be activated by the user.
>
> And why is it so hard to disable it once you find out where the annoying
> behavior comes from? (Just see how many articles deal with this specific issue;
> and having changed the name of the mode in 24.3 doesn't help)
What you say is generally applicable to any electric behavior in any
Emacs mode, not just to sh-electric-here-document-mode, right? Or is
that mode somehow special (and if so, how)?
next prev parent reply other threads:[~2015-02-20 8:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 8:19 Default setting for sh-maybe-here-document-mode Thibaut Verron
2015-02-20 8:31 ` Eli Zaretskii [this message]
2015-02-20 8:39 ` Thibaut Verron
2015-02-20 13:58 ` Stefan Monnier
2015-02-20 15:49 ` Thibaut Verron
2015-02-20 17:08 ` Stefan Monnier
2015-02-20 17:23 ` Thibaut Verron
2015-02-22 23:24 ` Stefan Monnier
2015-02-23 8:41 ` Thibaut Verron
2015-02-21 9:12 ` Philipp Stephani
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=83r3tlkmpx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=thibaut.verron@gmail.com \
/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.