bug#6941: 24.0.50; yank doesn't return latest kill

bug#6941: 24.0.50; yank doesn't return latest kill

[Andreas Röhler]

emacs -Q:

Hi,

with yank following a kill-new, Emacs doesn't yank the latest killed
string.

Checked it in a scratch buffer with following content after default:

abc foo bar
(kill-new (buffer-substring-no-properties 192 195) ==> "abc"
(kill-new (buffer-substring-no-properties 196 199) ==> "foo"
(kill-new (buffer-substring-no-properties 200 203) ==> "bar"

After evaluating this, following yank should insert "bar".

Instead it inserted some other, previously killed content.

AFAIS its related to activated region.
Doesn't happen, if a yank follows immediatly such a kill-new.
If region gets activated meanwhile by moving the cursor, content gets 
into the kill-ring and is yanked back instead ot the previous kill.


Thanks

Andreas

--
https://code.launchpad.net/~a-roehler/python-mode
https://code.launchpad.net/s-x-emacs-werkstatt/

In GNU Emacs 24.0.50.1 (i686-pc-linux-gnu, GTK+ Version 2.12.0)
  of 2010-08-28

Windowing system distributor `The X.Org Foundation', version 11.0.70200000
Important settings:
   value of $LC_ALL: nil
   value of $LC_COLLATE: nil
   value of $LC_CTYPE: nil
   value of $LC_MESSAGES: nil
   value of $LC_MONETARY: nil
   value of $LC_NUMERIC: nil
   value of $LC_TIME: nil
   value of $LANG: de_DE.UTF-8
   value of $XMODIFIERS: @im=local
   locale-coding-system: utf-8-unix
   default enable-multibyte-characters: t

Major mode: Lisp Interaction

Minor modes in effect:
   tooltip-mode: t
   mouse-wheel-mode: t
   tool-bar-mode: t
   menu-bar-mode: t
   file-name-shadow-mode: t
   global-font-lock-mode: t
   font-lock-mode: t
   blink-cursor-mode: t
   auto-composition-mode: t
   auto-encryption-mode: t
   auto-compression-mode: t
   line-number-mode: t
   transient-mark-mode: t

Recent input:
<help-echo> <help-echo> <help-echo> <help-echo> <help-echo>
<help-echo> <help-echo> <help-echo> <help-echo> <help-echo>
<help-echo> <help-echo> <help-echo> <help-echo> <menu-bar>
<options> <menu-set-font> M-x i n s e r t - f i <tab>
<return> <M-backspace> <M-backspace> e i n . t x t
<return> C-k C-k C-k C-k C-k C-k C-k C-x C-f <up> <return>
C-k C-k C-k C-k C-k C-k C-k C-x C-s C-x k <return>
<down> C-e C-x C-e <down> C-x C-e <down> C-x C-e <return>
<return> C-y M-x r e p o r t . - <backspace> <backspace>
- e m a c s - b u <tab> <return>

Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.
Mark set
Loading vc-cvs...done
Loading vc-git...done
Saving file /home/speck/ein.txt...
Wrote /home/speck/ein.txt
"abc"
"foo"
"bar"
Mark set

Load-path shadows:
None found.

Features:
(shadow sort gnus-util mail-extr message sendmail regexp-opt rfc822 mml
easymenu mml-sec mm-decode mm-bodies mm-encode mail-parse rfc2231
rfc2047 rfc2045 ietf-drums mm-util mail-prsvr mailabbrev mail-utils
gmm-utils mailheader emacsbug vc-git vc-cvs tooltip ediff-hook vc-hooks
lisp-float-type mwheel x-win x-dnd tool-bar dnd fontset image fringe
lisp-mode register page menu-bar rfn-eshadow timer select scroll-bar
mldrag mouse jit-lock font-lock syntax facemenu font-core frame cham
georgian utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao
korean japanese hebrew greek romanian slovak czech european ethiopic
indian cyrillic chinese case-table epa-hook jka-cmpr-hook help simple
abbrev loaddefs button minibuffer faces cus-face files text-properties
overlay md5 base64 format env code-pages mule custom widget
hashtable-print-readable backquote make-network-process dbusbind
dynamic-setting system-font-setting font-render-setting move-toolbar gtk
x-toolkit x multi-tty emacs)

bug#6941: 24.0.50; yank doesn't return latest kill

[Jan Djärv]

2010-08-29 21:39, Andreas Röhler skrev:
>
> emacs -Q:
>
> Hi,
>
> with yank following a kill-new, Emacs doesn't yank the latest killed
> string.
>
> Checked it in a scratch buffer with following content after default:
>
> abc foo bar
> (kill-new (buffer-substring-no-properties 192 195) ==> "abc"
> (kill-new (buffer-substring-no-properties 196 199) ==> "foo"
> (kill-new (buffer-substring-no-properties 200 203) ==> "bar"
>
> After evaluating this, following yank should insert "bar".
>
> Instead it inserted some other, previously killed content.
>

If I add the missing ) to those expressions, I do get bar yanked.
Try again with proper expressions.

	Jan D.

bug#6941: 24.0.50; yank doesn't return latest kill

[Andreas Röhler]

Am 30.08.2010 15:37, schrieb Jan Djärv:
> 2010-08-29 21:39, Andreas Röhler skrev:
>>
>> emacs -Q:
>>
>> Hi,
>>
>> with yank following a kill-new, Emacs doesn't yank the latest killed
>> string.
>>
>> Checked it in a scratch buffer with following content after default:
>>
>> abc foo bar
>> (kill-new (buffer-substring-no-properties 192 195) ==> "abc"
>> (kill-new (buffer-substring-no-properties 196 199) ==> "foo"
>> (kill-new (buffer-substring-no-properties 200 203) ==> "bar"
>>
>> After evaluating this, following yank should insert "bar".
>>
>> Instead it inserted some other, previously killed content.
>>
>
> If I add the missing ) to those expressions, I do get bar yanked.
> Try again with proper expressions.
>
> Jan D.
>

Hi,

sorry for the typo.

I'm coming upon from functions which exchange-point-and-mark in order to 
get the string found displayed. Seems it's the setting of the mark, 
which triggers the bug.

If the last line is changed into

(kill-new (buffer-substring-no-properties 200 203)) asdf

evaluating it before "asdf", push-mark, down one or more line, region is 
active, yank, "asdf" is inserted.


Which follows the setting of select-active-regions, please see my 
posting to emacs-devel.

Basically it's a design-flaw IMHO.

Thanks

Andreas

bug#6941: 24.0.50; yank doesn't return latest kill

[Chong Yidong]

Andreas Röhler <andreas.roehler@easy-emacs.de> writes:

> I'm coming upon from functions which exchange-point-and-mark in order
> to get the string found displayed. Seems it's the setting of the mark,
> which triggers the bug.
>
> If the last line is changed into
>
> (kill-new (buffer-substring-no-properties 200 203)) asdf
>
> evaluating it before "asdf", push-mark, down one or more line, region
> is active, yank, "asdf" is inserted.

Your description is still too vague.  Please provide a step by step
recipe; don't describe what you did ("evaluating", "push-mark", etc.),
but what you typed.  For instance, here is what I did:

1. emacs -Q
2. Type the following: (kill-new (buffer-substring-no-properties 193 197))
3. C-x C-e

     => "kill" appears in the echo area

4. M-<
5. C-SPC
6. C-n
7. C-y

     => The word "kill" is yanked into the buffer.

I don't see any bug here.

bug#6941: 24.0.50; yank doesn't return latest kill

[Andreas Röhler]

Am 31.08.2010 18:12, schrieb Chong Yidong:
> Andreas Röhler<andreas.roehler@easy-emacs.de>  writes:
>
>> I'm coming upon from functions which exchange-point-and-mark in order
>> to get the string found displayed. Seems it's the setting of the mark,
>> which triggers the bug.
>>
>> If the last line is changed into
>>
>> (kill-new (buffer-substring-no-properties 200 203)) asdf
>>
>> evaluating it before "asdf", push-mark, down one or more line, region
>> is active, yank, "asdf" is inserted.
>
> Your description is still too vague.  Please provide a step by step
> recipe; don't describe what you did ("evaluating", "push-mark", etc.),
> but what you typed.  For instance, here is what I did:
>
> 1. emacs -Q
> 2. Type the following: (kill-new (buffer-substring-no-properties 193 197))
> 3. C-x C-e
>
>       =>  "kill" appears in the echo area
>
> 4. M-<
> 5. C-SPC
> 6. C-n
> 7. C-y
>
>       =>  The word "kill" is yanked into the buffer.
>
> I don't see any bug here.
>

Unfortunatly it behaves different here.

Get twofold

;; This buffer is for notes you don't want to save, and for Lisp evaluation.
;; This buffer is for notes you don't want to save, and for Lisp evaluation.

instead, which is logically, as C-n after C-SPC activated the region.

Just as a default it's a bug....

BTW I run it from an uninstalled Emacs from the directory where it's 
built with bootstrap.

Andreas

bug#6941: 24.0.50; yank doesn't return latest kill

[Chong Yidong]

Andreas Röhler <andreas.roehler@easy-emacs.de> writes:

> Unfortunatly it behaves different here.
>
> Get twofold
>
> ;; This buffer is for notes you don't want to save, and for Lisp evaluation.
> ;; This buffer is for notes you don't want to save, and for Lisp evaluation.
>
> instead, which is logically, as C-n after C-SPC activated the region.

It's not logical, since C-y only pastes yanks the clipboard or the
kill-ring; it no longer yanks the primary selection.  C-n after C-SPEC
actives the region, but that only sets the primary selection.

Either you are not running with `emacs -Q', or your repository is not up
to date for some reason, or something external to Emacs (maybe a
misbehaving selection manager?) is screwing up.

bug#6941: 24.0.50; yank doesn't return latest kill

[Andreas Röhler]

Am 31.08.2010 19:57, schrieb Chong Yidong:
> Andreas Röhler<andreas.roehler@easy-emacs.de>  writes:
>
>> Unfortunatly it behaves different here.
>>
>> Get twofold
>>
>> ;; This buffer is for notes you don't want to save, and for Lisp evaluation.
>> ;; This buffer is for notes you don't want to save, and for Lisp evaluation.
>>
>> instead, which is logically, as C-n after C-SPC activated the region.
>
> It's not logical, since C-y only pastes yanks the clipboard or the
> kill-ring; it no longer yanks the primary selection.

AFAIS the clipboard is yanked back - uncomfortably so far.

  C-n after C-SPEC
> actives the region, but that only sets the primary selection.
>
> Either you are not running with `emacs -Q',

initial bug report should reveil this, if that's the case.


or your repository is not up
> to date for some reason,

its from here:
git clone git://repo.or.cz/org-mode.git

can't imagine that clone the responsible

or something external to Emacs (maybe a
> misbehaving selection manager?) is screwing up.
>

bug#6941: 24.0.50; yank doesn't return latest kill

[Chong Yidong]

>> or something external to Emacs (maybe a
>> misbehaving selection manager?) is screwing up.

Looks like this is the cause (Klipper synchronizing the clipboard and
primary).

Since this is not an Emacs issue, I am closing the bug.

bug#6941: 24.0.50; yank doesn't return latest kill

[Andreas Röhler]

Am 02.09.2010 17:17, schrieb Chong Yidong:
>>> or something external to Emacs (maybe a
>>> misbehaving selection manager?) is screwing up.
>
> Looks like this is the cause (Klipper synchronizing the clipboard and
> primary).
>
> Since this is not an Emacs issue, I am closing the bug.
>


Bug doesn't show up any more with build from today.
Which points to another reason then KDE though.

GNU Emacs 23.1.92.1 (i686-pc-linux-gnu, GTK+ Version 2.12.0) of 2010-02-19

bug#6941: 24.0.50; yank doesn't return latest kill

[Andreas Röhler]

Am 02.09.2010 17:17, schrieb Chong Yidong:
>>> or something external to Emacs (maybe a
>>> misbehaving selection manager?) is screwing up.
>
> Looks like this is the cause (Klipper synchronizing the clipboard and
> primary).
>
> Since this is not an Emacs issue, I am closing the bug.
>

Sorry, got the wrong Emacs before.

Ie bug persists.

Setting select-active-regions not t solves it.