From: Drew Adams <drew.adams@oracle.com>
To: Emacs-devel <emacs-devel@gnu.org>
Subject: Why change the advertised bindings of Isearch commands?
Date: Thu, 26 Nov 2015 10:45:42 -0800 (PST) [thread overview]
Message-ID: <98f8a71f-1f10-4ff6-a4c1-8dc2d179b84b@default> (raw)
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?
IOW, why this?
(put 'isearch-toggle-case-fold :advertised-binding "\M-sc")
(put 'isearch-toggle-regexp :advertised-binding "\M-sr")
(put 'isearch-edit-string :advertised-binding "\M-se")
I do not think this is an improvement for users.
If the aim was to let users know that they _can_ find such
commands on the common prefix `M-s' (which is fine), that
information is available in other ways. For one thing, it
is trivial to do `M-s C-h' during Isearch, to see all of
the `M-s' bindings.
Let's please not advertise these more complex bindings in
favor of the longstanding, simple ones (thankfully still
usable).
next reply other threads:[~2015-11-26 18:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 18:45 Drew Adams [this message]
2015-11-26 23:16 ` Why change the advertised bindings of Isearch commands? Juri Linkov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=98f8a71f-1f10-4ff6-a4c1-8dc2d179b84b@default \
--to=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 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.