[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#46689: 28.0.50; Behavior changed in latest Gcc Emacs
From: |
Lars Ingebrigtsen |
Subject: |
bug#46689: 28.0.50; Behavior changed in latest Gcc Emacs |
Date: |
Sun, 19 Jun 2022 15:50:00 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
Violin Learner <zhao.york@gmail.com> writes:
> In the latest Gcc Emacs, selecting some text within Emacs will change the
> result of
> (current-kill 0). However, the old behavior was that only selecting text in
> the external
> programs other than Emacs would change what (current-kill 0) returns.
>
> Reproduce steps:
>
> 1. Evaluate (setq select-enable-primary t)
> 2. Evaluate (current-kill 0), and note the result
> 3. Hit C-<SPC>, move the cursor to select some text
> 4. Evaluate (current-kill 0) again, and the result will be the text just been
> selected in
> step 3. However, the result used to be the same as in step 2.
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
I'm unable to reproduce this behaviour now. Do you still see this in
recent Emacs versions?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#46689: 28.0.50; Behavior changed in latest Gcc Emacs,
Lars Ingebrigtsen <=