unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: monnier@iro.umontreal.ca, 27442@debbugs.gnu.org, Hi-Angel@yandex.ru
Subject: bug#27442: Un-obsolete x-clipboard-yank, or provide analogous functional
Date: Tue, 06 Jul 2021 18:45:15 +0300	[thread overview]
Message-ID: <83im1nfnuc.fsf@gnu.org> (raw)
In-Reply-To: <87bl7fv845.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue,  06 Jul 2021 16:18:18 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: monnier@iro.umontreal.ca,  Hi-Angel@yandex.ru,  27442@debbugs.gnu.org
> Date: Tue, 06 Jul 2021 16:18:18 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> Hm...  I don't really see any with our current low-level
> >> functions.  I think x-get-selection-internal could have returned more
> >> metadata -- the timestamp, for instance, which would have allowed us to
> >> see whether we ourselves really pushed the data to the clipboard.
> >
> > Where would that time stamp come from?
> 
> Selections have time stamps

In the clipboard? supported by all the systems and all the clipboard
varieties out there?

> so we could compare the time stamp from
> when we pushed the data onto the clipboard with what we have.  I think?

Is it reasonable to assume that close enough time stamps necessarily
mean we are the owner?

> > I admit I don't really understand what the patch does and how.  can
> > you elaborate on that?
> 
> It just makes `M-x clipboard-yank' defeat the "check for duplicates"
> logic and always return the contents of the clipboard.

But that would mean we throw away the baby together with the
bathwater, no?  Why would we want to do that?





  reply	other threads:[~2021-07-06 15:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21 14:29 bug#27442: Un-obsolete x-clipboard-yank, or provide analogous functional Constantine Kharlamov
2017-06-21 19:10 ` Eli Zaretskii
2017-06-21 19:55   ` Constantine Kharlamov
2021-07-05 14:13     ` Lars Ingebrigtsen
2021-07-05 14:46       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-05 15:28         ` Lars Ingebrigtsen
2021-07-05 15:59           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-05 16:55           ` Eli Zaretskii
2021-07-05 20:11             ` Lars Ingebrigtsen
2021-07-05 20:24               ` Lars Ingebrigtsen
2021-07-06 11:21               ` Eli Zaretskii
2021-07-06 14:18                 ` Lars Ingebrigtsen
2021-07-06 15:45                   ` Eli Zaretskii [this message]
2021-07-06 16:20                     ` Lars Ingebrigtsen
2021-07-06 17:15                       ` Eli Zaretskii
2021-07-06 17:26                         ` Lars Ingebrigtsen

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=83im1nfnuc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=27442@debbugs.gnu.org \
    --cc=Hi-Angel@yandex.ru \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    /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).