From: gnu.emacs.bug@wongs.net
To: 8183@debbugs.gnu.org
Subject: bug#8183: isearch yanking
Date: Sat, 5 Mar 2011 16:03:52 -0800 [thread overview]
Message-ID: <AANLkTikku0rP_Cd4Y9LpKE2GF2-UbhuCog2AOMR4i=Gq@mail.gmail.com> (raw)
Hello!
I just spent a while trying to track down a bug in isearch.el that
turned out to be a "feature". C-y has been hijacked to do some weird
thing where it pastes the entire next line of the buffer instead of
the kill ring. (Wacky!)
Please change it so that C-y works normally.
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.
Additionally, the way isearch is remapping the C-y key breaks Emacs's
consistency. One of the wonderful things about Emacs is that it is
not modal. The basic keys always work the same regardless of what
"mode" you are in.
If you are not convinced, please consider that cut and paste is
fundamental to Emacs. C-y is so basic to how Emacs functions that
it's been listed in the Emacs tutorial (C-h t) for a quarter century.
The keybindings mentioned in the tutorial shouldn't be altered
lightly.
And finally, think about what a pain it is to teach people new to
Emacs that C-y works as yank and M-y is yank-pop, EXCEPT when doing a
search where M-y is yank and there is no way to do a yank-pop. This
one small quirk has added work not only on to people who are trying to
learn Emacs, but on to the people teaching Emacs and trying to write
easy to understand documentation and tutorials.
Fortunately, the fix for this is easy. In isearch.el, just change the
line that defines C-y as isearch-yank-line to isearch-yank-kill.
- (define-key map "\C-y" 'isearch-yank-line)
+ (define-key map "\C-y" 'isearch-yank-kill)
Thank you,
--B. Wong
next reply other threads:[~2011-03-06 0:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-06 0:03 gnu.emacs.bug [this message]
2011-03-06 0:23 ` bug#8183: isearch yanking Chong Yidong
[not found] ` <87bp1pf664.fsf@stupidchicken.com>
2011-03-06 0:27 ` Lennart Borgman
2011-03-06 5:33 ` Stefan Monnier
[not found] ` <jwvei6kstiq.fsf-monnier+emacs@gnu.org>
2011-03-06 14:05 ` Dani Moncayo
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='AANLkTikku0rP_Cd4Y9LpKE2GF2-UbhuCog2AOMR4i=Gq@mail.gmail.com' \
--to=gnu.emacs.bug@wongs.net \
--cc=8183@debbugs.gnu.org \
/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).