From: Juri Linkov <juri@linkov.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: Emacs-devel <emacs-devel@gnu.org>
Subject: Re: Why change the advertised bindings of Isearch commands?
Date: Fri, 27 Nov 2015 01:16:03 +0200 [thread overview]
Message-ID: <87ziy05p3g.fsf@mail.linkov.net> (raw)
In-Reply-To: <98f8a71f-1f10-4ff6-a4c1-8dc2d179b84b@default> (Drew Adams's message of "Thu, 26 Nov 2015 10:45:42 -0800 (PST)")
> In Isearch, these key bindings have long been in effect,
> and they are still in effect:
>
> M-e - isearch-edit-string
> M-c - isearch-toggle-case-fold
> M-r - isearch-toggle-regexp
>
> These keys are far easier to use than M-s c, M-s r, M-s e.
> So why have we changed the advertised bindings to be these
> more complex keys?
0. emacs -Q
1. C-h c M-e - M-e runs the command forward-sentence
2. C-h c M-c - M-c runs the command capitalize-word
3. C-h c M-r - M-r runs the command move-to-window-line-top-bottom
IOW, those are keys that are more useful to exit Isearch and do
what they do normally, thus advertising the new bindings will help
to get rid of old bindings in later releases.
next prev parent reply other threads:[~2015-11-26 23:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 18:45 Why change the advertised bindings of Isearch commands? Drew Adams
2015-11-26 23:16 ` Juri Linkov [this message]
2015-11-27 0:03 ` Drew Adams
2015-11-27 7:58 ` Eli Zaretskii
2015-11-28 5:33 ` Richard Stallman
2015-11-28 20:30 ` John Wiegley
[not found] <<98f8a71f-1f10-4ff6-a4c1-8dc2d179b84b@default>
[not found] ` <<87ziy05p3g.fsf@mail.linkov.net>
[not found] ` <<1a6f342a-3e59-4555-a345-e518cc598299@default>
[not found] ` <<83egfbub4q.fsf@gnu.org>
2015-11-27 9:33 ` Drew Adams
2015-11-27 10:16 ` Eli Zaretskii
[not found] <<dddad317-4c44-4a68-b1d3-19bbd3a6746f@default>
[not found] ` <<83k2p3sq71.fsf@gnu.org>
2015-11-27 16:50 ` Drew Adams
2015-11-27 23:09 ` Juri Linkov
2015-11-28 1:01 ` Drew Adams
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=87ziy05p3g.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=drew.adams@oracle.com \
--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).