From: Glenn Morris <rgm@gnu.org>
To: "Aaron S. Hawley" <aaron.s.hawley@gmail.com>
Cc: 10654@debbugs.gnu.org
Subject: bug#10654: 24.0.93; isearch-yank-line moved from C-y
Date: Mon, 30 Jan 2012 13:54:16 -0500 [thread overview]
Message-ID: <1a8vkp9g2v.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAFw1JJ6QAeB0+yrNW7M2RyO0KoVBzMFd2PDv7DHJo1tKA1_9OA@mail.gmail.com> (Aaron S. Hawley's message of "Mon, 30 Jan 2012 10:16:06 -0500")
"Aaron S. Hawley" wrote:
> I don't have any data to support that C-y is popular.
The weight of opinion seems to be against you.
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=7700#11
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.
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8183#5
While I'm sure there's someone in the world who has a use for
searching for the entire next line, there are many, many more people
who find it useful to search for items from the kill ring.
http://lists.gnu.org/archive/html/emacs-devel/2008-11/msg00687.html
I was reluctant about it in the first place.
> I can confirm that putting `isearch-yank-line' to the `M-s C-e'
> binding is unsatisfying (M-s C-k makes more sense).
Here is the motivation:
http://lists.gnu.org/archive/html/emacs-devel/2008-11/msg00606.html
bind `isearch-yank-line' to `M-s C-e' because `move-end-of-line' is
on `C-e'.
> Though, without any data maybe I'm the only person who uses it and
> needs a short key binding?
[...]
> How about the shorter (and obvious) key binding of C-k?
[...]
> (define-key isearch-mode-map "\C-k" 'isearch-yank-line)
Personally I have no opinion.
next prev parent reply other threads:[~2012-01-30 18:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 15:16 bug#10654: 24.0.93; isearch-yank-line moved from C-y Aaron S. Hawley
2012-01-30 18:54 ` Glenn Morris [this message]
2012-01-30 20:19 ` Aaron S. Hawley
2012-02-03 17:48 ` Kevin Rodgers
2012-02-04 0:17 ` Juri Linkov
2022-01-27 16:42 ` Lars Ingebrigtsen
2012-01-30 22:59 ` Juri Linkov
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=1a8vkp9g2v.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=10654@debbugs.gnu.org \
--cc=aaron.s.hawley@gmail.com \
/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).