unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>
Cc: Emacs-devel <emacs-devel@gnu.org>
Subject: RE: Why change the advertised bindings of Isearch commands?
Date: Thu, 26 Nov 2015 16:03:28 -0800 (PST)	[thread overview]
Message-ID: <1a6f342a-3e59-4555-a345-e518cc598299@default> (raw)
In-Reply-To: <87ziy05p3g.fsf@mail.linkov.net>

> > 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.

I disagree that we should remove those keys from the realm of
Isearch just because they have global bindings.  There are many,
many keys that you can use to exit Isearch.  And different users
use different such keys to exit.  And different users care to
have different keys exit and act immediately.

I see no reason to add these keys, by default, to the list
of keys that exit Isearch.

Any user who is that much a fan of performing any of those
global actions without first quitting Isearch can of course
bind them herself in the Isearch map - as has always been the
case.  That is trivial to do.

These keys perform important and commonly used Isearch actions,
and they should be kept for Isearch, as is.  This kind of
change is gratuitous (it has not been demanded by users), and
is a step backward.  IMHO.

I don't mind that the commands are _added_ to the `M-s' prefix.
What is wrong is to make those more complex bindings the
advertised bindings.

At the point where Emacs Dev has actually decided to remove
these short keys, for some reason, presumably that removal
will be part of a more interesting set of features.  And at
that point, if it ever comes, there would be no need to
advertise the complicated keys, as the quicker keys would
be gone.

This change is premature and uncalled for, IMHO.



  reply	other threads:[~2015-11-27  0:03 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
2015-11-27  0:03   ` Drew Adams [this message]
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=1a6f342a-3e59-4555-a345-e518cc598299@default \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.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).