From: "Andrew W. Nosenko" <andrew.w.nosenko@gmail.com>
To: Alan Mackenzie <acm@muc.de>
Cc: 7700@debbugs.gnu.org
Subject: bug#7700: 24.0.50; C-y binding withing Isearch mode
Date: Mon, 27 Dec 2010 01:13:07 +0200 [thread overview]
Message-ID: <AANLkTi=UsQDYH_R2nYvUsKx6mPn2W59kiwpHBBU48Akr@mail.gmail.com> (raw)
In-Reply-To: <20101223171434.GA3971@muc.de>
On Thu, Dec 23, 2010 at 19:14, Alan Mackenzie <acm@muc.de> wrote:
> Hi, Stefan,
>
> On Thu, Dec 23, 2010 at 10:30:50AM -0500, Stefan Monnier wrote:
>> > Personally, I find this behavior inconsistent/annoying: I would expect that
>> > C-y within Isearch add text X to the search text, where X is the text that
>> > would be yanked in normal editing.
>
>> FWIW, I'd agree. I've always found the C-y binding in isearch "useless"
>> and counter-intuitive. I'd much rather make C-y and M-y behave like
>> they do in the minibuffer.
>
> I use C-y ("grab to next end of line") quite a bit. But it annoys me
> that it's bound to C-y. I'd prefer C-y to do what M-y currently does,
> but please don't unbind "grab to end of line" completely. How about
> swapping C-y and M-y, like the OP suggested?
C-e and C-E (aka Ctrl-E and Ctrl-Shift-E)? C-e because I see no
useful meaning for "go to the end-of-line" inside isearch (if don't
count the real break isearch and go to the end of line), and C-E for
people with CUA "instincts".
--
Andrew W. Nosenko <andrew.w.nosenko@gmail.com>
next prev parent reply other threads:[~2010-12-26 23:13 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 19:06 bug#7700: 24.0.50; C-y binding withing Isearch mode Dani Moncayo
2010-12-21 21:26 ` Dani Moncayo
2010-12-23 15:30 ` Stefan Monnier
2010-12-23 16:09 ` Lennart Borgman
2010-12-23 16:46 ` Leo
2010-12-23 17:05 ` Andreas Schwab
2010-12-23 22:39 ` Leo
2010-12-23 17:14 ` Alan Mackenzie
2010-12-24 2:39 ` Stefan Monnier
2010-12-24 3:25 ` Lennart Borgman
2010-12-24 11:39 ` Dani Moncayo
2010-12-24 12:13 ` Lennart Borgman
2010-12-24 13:34 ` Dani Moncayo
2010-12-25 2:38 ` Juri Linkov
2010-12-25 4:06 ` Stefan Monnier
2010-12-25 11:15 ` Dani Moncayo
2010-12-25 19:52 ` Stefan Monnier
2010-12-25 20:09 ` Lennart Borgman
2010-12-27 22:15 ` Alan Mackenzie
2010-12-27 22:36 ` Drew Adams
2010-12-28 0:14 ` Lennart Borgman
2010-12-28 0:51 ` Drew Adams
2010-12-28 1:34 ` Lennart Borgman
2010-12-28 5:43 ` Drew Adams
2010-12-26 23:13 ` Andrew W. Nosenko [this message]
2010-12-26 23:33 ` Andrew W. Nosenko
2010-12-23 17:28 ` Drew Adams
2010-12-23 19:23 ` Alan Mackenzie
2010-12-23 19:30 ` Dani Moncayo
2010-12-23 20:48 ` Drew Adams
2010-12-23 20:58 ` Lennart Borgman
2010-12-23 21:28 ` Alan Mackenzie
2010-12-23 22:28 ` Drew Adams
2010-12-23 23:08 ` Dani Moncayo
2010-12-25 2:34 ` Juri Linkov
2010-12-25 4:07 ` Stefan Monnier
2010-12-23 20:46 ` Drew Adams
2010-12-23 19:48 ` Juri Linkov
2011-05-16 15:11 ` bug#7700: 24.0.50; C-y binding in " Dani Moncayo
2011-05-16 15:42 ` Stefan Monnier
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='AANLkTi=UsQDYH_R2nYvUsKx6mPn2W59kiwpHBBU48Akr@mail.gmail.com' \
--to=andrew.w.nosenko@gmail.com \
--cc=7700@debbugs.gnu.org \
--cc=acm@muc.de \
/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).