From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: RE: Why change the advertised bindings of Isearch commands?
Date: Fri, 27 Nov 2015 17:01:39 -0800 (PST) [thread overview]
Message-ID: <e6b2aa53-1f89-4794-afd0-bb76069b4c9d@default> (raw)
In-Reply-To: <87k2p3ghuv.fsf@mail.linkov.net>
> >> And evidently, the desire to remove it means we think its
> >> binding outside Isearch is more useful.
> >
> > We do? How and when did we decide that?
> >
> > What were the arguments pro and con - where can I find the
> > discussion? Did we poll the users, to get their take on this?
>
> You can find the discussion that you missed in the mail archive.
Could you possibly please point to it?
Subject? month? year? keywords? I searched quickly (and unsuccessfully) for "capitalize" over the last 8 years, but
a pointer would help.
> > And that I disagree with. But if it _has_ been discussed and
> > decided then I have no problem supporting the decision, even
> > if I disagree with it.
>
> I remember that the consensus was to reduce the number of
> Isearch keys that override their global bindings.
A consensus, huh? And these particular keys were discussed,
and decided on? I'd like to see that discussion.
next prev parent reply other threads:[~2015-11-28 1:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<dddad317-4c44-4a68-b1d3-19bbd3a6746f@default>
[not found] ` <<83k2p3sq71.fsf@gnu.org>
2015-11-27 16:50 ` Why change the advertised bindings of Isearch commands? Drew Adams
2015-11-27 23:09 ` Juri Linkov
2015-11-28 1:01 ` Drew Adams [this message]
[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
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=e6b2aa53-1f89-4794-afd0-bb76069b4c9d@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).