GNU bug report logs - #6637
24.0.50; kill ring being seriously polluted

Previous Next

Package: emacs;

Reported by: Tim Van Holder <tim.vanholder <at> gmail.com>

Date: Thu, 15 Jul 2010 08:51:01 UTC

Severity: normal

Found in version 24.0.50

Done: Chong Yidong <cyd <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #23 received at 6637 <at> debbugs.gnu.org (full text, mbox):

From: Chong Yidong <cyd <at> stupidchicken.com>
To: Tim Van Holder <tim.vanholder <at> gmail.com>
Cc: 6637 <at> debbugs.gnu.org
Subject: Re: bug#6637: 24.0.50; kill ring being seriously polluted
Date: Fri, 16 Jul 2010 11:57:01 -0400
Tim Van Holder <tim.vanholder <at> gmail.com> writes:

> 1) emacs -Q
> 2) Holding the shift key, press the up arrow until you're at the top
> of the buffer
> 3) Release the shift key and press the down arrow until you're back at
> the bottom of the buffer
> 4) Press C-y
>
> This yanks in the comment lines, even though I at no point requested a
> kill or copy-as-kill.

Go to any X application (firefox, etc) with a text field.
Holding shift, press the arrow keys and select some text.
Release shift, and press another down arrow to deselect it.

In Emacs 23 (in the absence of latest changes):

Run `emacs -Q'.
C-y

The text you selected is yanked into the buffer.  This is because the
other X application put your selected text in the primary selection.
How is the behavior of Emacs' new shift selection different from the
other X application's shift selection?




This bug report was last modified 12 years and 292 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.