unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org, juri@linkov.net
Subject: RE: Why change the advertised bindings of Isearch commands?
Date: Fri, 27 Nov 2015 01:33:10 -0800 (PST)	[thread overview]
Message-ID: <dddad317-4c44-4a68-b1d3-19bbd3a6746f@default> (raw)
In-Reply-To: <<83egfbub4q.fsf@gnu.org>>

> > > 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.
>
> The issue is not how to exit Isearch.  The issue is how to go
> forward one sentence or capitalize a word while in Isearch.

Read what I said, please.  No one said that the "issue" is
"how to exit".  It's about changing the default behavior to
make these keys "exit and act immediately".

Using M-c to exit and capitalize means removing it as a key
that does something useful _in_ Isearch.

And the particular thing M-c does now, which we would
be losing it for, is a common Isearch action: toggle
case-fold. Likewise for the other keys.

> What you are saying is that a user who spots a word to be
> capitalized during Isearch needs to do at least 2 things:
> exit Isearch with some key, then type M-c.

Exactly as it has always been: `RET M-c'.

And not "at least 2 things".  Exactly 2 things: exit & act.
If you want to do something outside of Isearch you quit
Isearch and do it.  Nothing new here.

What you are saying is that a user who wants to toggle
case-fold should need to do 2 things: `M-s c'.  You might
say, "Six of one; half a dozen of the other."  Except that
one is the longstanding default, and was done for Isearch.
The other is one person's preference (so far).

The question (which IMO should have been raised, instead of
just implementing a change) is which is more useful for
most users of Isearch, most of the time.

So far, no reason for this change in defaults (for 3 keys)
was even given.  AFAIK, it ain't broke; no need to fix it.

Why change the default behavior for these particular keys
now?  And without any discussion or polling of users?

As I said, "different users care to have different keys
exit and act immediately".  It is trivial for a user to
make M-c exit and act immediately.

The default behavior makes sense to me.  I don't see a
crying need to reduce `RET M-c' to M-c and make users use
`M-s c' to toggle case sensitivity.

But let's hear some arguments in favor of the changes, please.



       reply	other threads:[~2015-11-27  9:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2015-11-27 10:16         ` Why change the advertised bindings of Isearch commands? 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
2015-11-26 18:45 Drew Adams
2015-11-26 23:16 ` 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

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=dddad317-4c44-4a68-b1d3-19bbd3a6746f@default \
    --to=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --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).