unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 8183@debbugs.gnu.org, gnu.emacs.bug@wongs.net, emacs-devel@gnu.org
Subject: bug#8183: isearch yanking
Date: Sun, 6 Mar 2011 01:27:09 +0100	[thread overview]
Message-ID: <AANLkTi=Yj1uN6xaO=06QDQ6=t3u9Ghng=bSunoHwGKEg__10127.2714011886$1299371826$gmane$org@mail.gmail.com> (raw)
In-Reply-To: <87bp1pf664.fsf@stupidchicken.com>

On Sun, Mar 6, 2011 at 1:23 AM, Chong Yidong <cyd@stupidchicken.com> wrote:
> gnu.emacs.bug@wongs.net writes:
>
>> 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!)
>
>> 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.
>
> This has been bugging me, and has been discussed before, e.g.
>
>  http://lists.gnu.org/archive/html/emacs-devel/2008-11/msg00485.html
>
> Back in that 2008 thread, Juri Linkov suggested exactly this change, and
> moving isearch-yank-line over to M-s C-e.
>
> Nothing seemed to come of that suggestion, maybe due to simple inertia.
> I now propose to make it so.  Any objections?

It might have stalled because we where discussing other changes to
isearch keymap, but I can see no reason to not make the proposed
change here.





  parent reply	other threads:[~2011-03-06  0:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-06  0:03 bug#8183: isearch yanking gnu.emacs.bug
2011-03-06  0:23 ` Chong Yidong
     [not found] ` <87bp1pf664.fsf@stupidchicken.com>
2011-03-06  0:27   ` Lennart Borgman [this message]
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='AANLkTi=Yj1uN6xaO=06QDQ6=t3u9Ghng=bSunoHwGKEg__10127.2714011886$1299371826$gmane$org@mail.gmail.com' \
    --to=lennart.borgman@gmail.com \
    --cc=8183@debbugs.gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=gnu.emacs.bug@wongs.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).