From: Lennart Borgman <lennart.borgman@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 7700@debbugs.gnu.org
Subject: bug#7700: 24.0.50; C-y binding withing Isearch mode
Date: Fri, 24 Dec 2010 04:25:42 +0100 [thread overview]
Message-ID: <AANLkTinRDg3KxEqXF5J+eFJSFZA4SHd-e5gKLh0j6ZcN@mail.gmail.com> (raw)
In-Reply-To: <jwvk4izlwtn.fsf-monnier+emacs@gnu.org>
On Fri, Dec 24, 2010 at 3:39 AM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
>> I use C-y ("grab to next end of line") quite a bit.
>
> I'd much rather have a prefix key that lets me use any standard movement
> to select the text to grab from the buffer (so "<prefix> C-e" would do
> what C-y does and "<prefix> M-f" would do more or less what C-w does).
I like the logic/mnemonic but wouldn't it would be cumbersome to use it?
I suggest instead that any standard forward movement command while in
isearch forward mode should select the text to grab WITHOUT any prefix
key. For backward movement I suggest a similar logic.
Would not that be both easy to use and remember? (And I think the
logic is so easy for the mind that it would be quick to relearn. In
addition to this is rather similar to how extending the region works
which should make it even easier to remember.)
In addition to this I suggest that standard paste commands (i.e. C-y
yank/C-v cua-paste) paste into isearch search string.
And that M-y (i.e. yank-pop/cua-yank-pop) does the yank popping on the
isearch search string as suggested here.
next prev parent reply other threads:[~2010-12-24 3:25 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 [this message]
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
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=AANLkTinRDg3KxEqXF5J+eFJSFZA4SHd-e5gKLh0j6ZcN@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=7700@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).