From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Ignacio Casso <ignaciocasso@hotmail.com>, 53894@debbugs.gnu.org
Subject: bug#53894: 27.2; Clipboard copy -> C-y -> M-y -> Same clipboard copy does not push to kill ring
Date: Thu, 10 Feb 2022 09:56:08 +0800 [thread overview]
Message-ID: <87wni3zdqf.fsf@yahoo.com> (raw)
In-Reply-To: <87r18bg59w.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 09 Feb 2022 21:21:31 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Ignacio Casso <ignaciocasso@hotmail.com> writes:
>
>> This would also answer my original question: unless there was a
>> timestamp in the clipboard Emacs has indeed no way to know right now if
>> the exact same string was copied to the clipboard again in-between (in
>> which case I would expect it to be pushed to the top of the kill-ring
>> again)
>
> On X (at the very least), the clipboard does have a timestamp, though.
> But we don't use it, which seems like the bug here. Probably.
>
> Po Lu's done some work in this area lately; added to the CCs.
Every platform except MS-Windows has `x-selection-owner-p' or something
to that effect which tells Emacs whether or not it was the last program
to have saved to a selection (i.e., the clipboard, or the primary
selection.)
On the platforms where it does work reliably, Emacs uses it to determine
whether or not to return nil from the interprogram-paste-function, so I
don't see a problem here.
Eli says MS-Windows also does something similar, but using a different
mechanism.
Thanks.
next prev parent reply other threads:[~2022-02-10 1:56 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 9:13 bug#53894: 27.2; Clipboard copy -> C-y -> M-y -> Same clipboard copy does not push to kill ring Ignacio Casso
2022-02-09 11:44 ` Lars Ingebrigtsen
2022-02-09 12:52 ` Ignacio Casso
2022-02-09 20:21 ` Lars Ingebrigtsen
2022-02-10 1:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-02-10 6:20 ` Eli Zaretskii
2022-02-10 6:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-10 6:42 ` Lars Ingebrigtsen
2022-02-10 6:48 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-10 8:37 ` Lars Ingebrigtsen
2022-02-10 10:03 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-10 6:39 ` Lars Ingebrigtsen
2022-02-10 8:06 ` Eli Zaretskii
2022-02-10 8:43 ` Lars Ingebrigtsen
2022-02-10 10:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-10 11:37 ` Lars Ingebrigtsen
2022-02-10 12:08 ` Eli Zaretskii
2022-02-10 12:14 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-10 12:29 ` Eli Zaretskii
2022-02-10 12:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-10 12:49 ` Lars Ingebrigtsen
2022-02-10 13:20 ` Ignacio Casso
2022-02-11 1:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-11 10:24 ` Ignacio Casso
2022-02-11 11:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-11 11:28 ` Ignacio Casso
2022-02-11 12:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-11 12:42 ` Ignacio Casso
2022-02-11 12:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-12 2:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-27 18:57 ` Ignacio Casso
2022-02-28 1:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-28 12:12 ` Ignacio Casso
2022-02-28 13:35 ` Eli Zaretskii
2022-02-28 14:22 ` Ignacio Casso
2022-02-28 13:48 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-28 14:35 ` Ignacio Casso
[not found] ` <87wnhfoy5h.fsf@hotmail.com>
2022-02-28 16:10 ` Ignacio Casso
2022-03-01 0:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-01 7:51 ` Ignacio Casso
2022-03-01 13:19 ` Eli Zaretskii
2022-03-01 15:29 ` Ignacio Casso
2022-03-02 0:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-02 7:44 ` Ignacio Casso
2022-03-02 7:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-02 8:37 ` Ignacio Casso
2022-03-02 10:03 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-09 7:41 ` Ignacio Casso
2022-03-09 13:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-24 19:59 ` Ignacio Casso
2022-03-25 6:25 ` Eli Zaretskii
2022-03-29 12:01 ` Ignacio Casso
2022-03-29 13:00 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-01 10:15 ` Ignacio Casso
2022-04-01 10:59 ` Eli Zaretskii
2022-04-01 11:23 ` Ignacio Casso
2022-04-01 12:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-01 12:15 ` Eli Zaretskii
2022-04-01 12:57 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-01 12:10 ` Eli Zaretskii
2022-03-01 15:19 ` Lars Ingebrigtsen
[not found] ` <871qznc4qg.fsf@hotmail.com>
2022-02-28 16:56 ` Ignacio Casso
[not found] ` <87v8xl376s.fsf@hotmail.com>
2022-02-11 12:48 ` Ignacio Casso
[not found] ` <87pmnurelg.fsf@hotmail.com>
2022-02-10 14:29 ` Ignacio Casso
2022-02-11 6:15 ` Lars Ingebrigtsen
2022-02-11 8:16 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wni3zdqf.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=53894@debbugs.gnu.org \
--cc=ignaciocasso@hotmail.com \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.