Subject: bug#27442: Un-obsolete x-clipboard-yank, or provide analogous functional

From: Lars Ingebrigtsen <[email-masked]>
Date: Mon, 05 Jul 2021 22:24:15 +0200

Lars Ingebrigtsen <[email-masked]> writes:

> Because we're copying over the string to the clipboard.  So when we're
> then yanking back, we're really trying to determine whether we ourselves
> was responsible for putting the data on the clipboard, and if that's the
> case, we want to ignore the data?  Because:
>
> (kill-new "foo")
> (gui-selection-value)
> => nil

If this is the reason for this check, then removing the setq of 
gui--last-selected-text-clipboard in gui-selection-value, and only set
it in gui-select-text, would fix this problem, too.  I think.

But it's late, and I may be misreading the code.  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no