[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Why change the advertised bindings of Isearch commands?
From: |
Eli Zaretskii |
Subject: |
Re: Why change the advertised bindings of Isearch commands? |
Date: |
Fri, 27 Nov 2015 12:16:02 +0200 |
> Date: Fri, 27 Nov 2015 01:33:10 -0800 (PST)
> From: Drew Adams <address@hidden>
> Cc: address@hidden, address@hidden
>
> > > > 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".
Read what _I_ said, please. I was describing the issue Jury alluded
to.
> Using M-c to exit and capitalize means removing it as a key
> that does something useful _in_ Isearch.
And evidently, the desire to remove it means we think its binding
outside Isearch is more useful.
> 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.
You have an alternative for that.
> > 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'.
The intent of the advertised bindings is to change that at some future
point.
> And not "at least 2 things". Exactly 2 things: exit & act.
No, it's "at least 2 things". Because depending on how you exit
Isearch you may need to move point first.
> 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.
That's a different issue. You asked why the advertised bindings were
changed; you now have the answer, I hope.
> As I said, "different users care to have different keys
> exit and act immediately".
There are facilities to tailor the commands that exit Isearch, if the
user doesn't like the defaults.
> But let's hear some arguments in favor of the changes, please.
That's a separate discussion.
- Why change the advertised bindings of Isearch commands?, Drew Adams, 2015/11/26
- Re: Why change the advertised bindings of Isearch commands?, Juri Linkov, 2015/11/26
- RE: Why change the advertised bindings of Isearch commands?, Drew Adams, 2015/11/26
- Re: Why change the advertised bindings of Isearch commands?, Eli Zaretskii, 2015/11/27
- RE: Why change the advertised bindings of Isearch commands?, Drew Adams, 2015/11/27
- Re: Why change the advertised bindings of Isearch commands?,
Eli Zaretskii <=
- RE: Why change the advertised bindings of Isearch commands?, Drew Adams, 2015/11/27
- Re: Why change the advertised bindings of Isearch commands?, Juri Linkov, 2015/11/27
- RE: Why change the advertised bindings of Isearch commands?, Drew Adams, 2015/11/27
- Re: Why change the advertised bindings of Isearch commands?, Richard Stallman, 2015/11/28
- Re: Why change the advertised bindings of Isearch commands?, John Wiegley, 2015/11/28