GNU bug report logs - #73830
using one expression to make multiple X selections

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 73830 in the body.
You can then email your comments to 73830 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: libreville <libreville <at> riseup.net>
To: bug-gnu-emacs <at> gnu.org
Subject: Re: using one expression to make multiple X selections
Date: Tue, 15 Oct 2024 18:04:36 +0000

My apologies, that should of course have read "sleep-for 1", not
"wait-for 1".

On 2024-10-15 13:59, libreville wrote:

> 
> (progn 
>   (gui-set-selection 'CLIPBOARD "3")
>   (wait-for 1)
>   (gui-set-selection 'CLIPBOARD "4"))
> 

Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):

From: libreville <libreville <at> riseup.net>
To: bug-gnu-emacs <at> gnu.org
Subject: Re: using one expression to make multiple X selections
Date: Wed, 16 Oct 2024 19:42:54 +0000

Hi there,

going by the list archive, my first email didn't go through. Here it is
again in case that's right:


Hello,

I stumbled on this while trying to elisp a few things into my X
clipboard manager. Evaluating these two expressions in turn:

(gui-set-selection 'CLIPBOARD "1")
(gui-set-selection 'CLIPBOARD "2")

results in both "1" and "2" being saved to the clipboard history.
However:

(progn
  (gui-set-selection 'CLIPBOARD "1")
  (gui-set-selection 'CLIPBOARD "2"))

results in "2" being saved to the clipboard history but, contrary to
what I would expect, not "1". On the other hand this:

(progn
  (gui-set-selection 'CLIPBOARD "3")
  (sleep-for 1)
  (gui-set-selection 'CLIPBOARD "4"))

gets both "3" and "4" onto the clipboard (history). I get similar
results with kill-new in place of gui-set-selection 'CLIBOARD and with
other ways of grouping the two kills into one expression.

Why does waiting work around the problem?

Tested with both copyq and clipman / Emacs 28.2 / Xfce.

Best,

liv.



On 2024-10-15 18:04, libreville wrote:
> My apologies, that should of course have read "sleep-for 1", not
> "wait-for 1".
> 
> On 2024-10-15 13:59, libreville wrote:
> 
>> 
>> (progn 
>>   (gui-set-selection 'CLIPBOARD "3")
>>   (wait-for 1)
>>   (gui-set-selection 'CLIPBOARD "4"))
>>

Message #11 received at 73830 <at> debbugs.gnu.org (full text, mbox):

From: Jeremy Bryant <jb <at> jeremybryant.net>
To: libreville <libreville <at> riseup.net>
Cc: 73830 <at> debbugs.gnu.org
Subject: Re: bug#73830: using one expression to make multiple X selections
Date: Wed, 16 Oct 2024 22:54:59 +0100

libreville <libreville <at> riseup.net> writes:

>
> Why does waiting work around the problem?
>
> Tested with both copyq and clipman / Emacs 28.2 / Xfce.

Have you tried with a more recent version of Emacs?

Message #14 received at 73830 <at> debbugs.gnu.org (full text, mbox):

From: Po Lu <luangruo <at> yahoo.com>
To: libreville <libreville <at> riseup.net>
Cc: 73830 <at> debbugs.gnu.org
Subject: Re: bug#73830: using one expression to make multiple X selections
Date: Thu, 17 Oct 2024 07:49:13 +0800

libreville <libreville <at> riseup.net> writes:

> Hi there,
>
> going by the list archive, my first email didn't go through. Here it is
> again in case that's right:
>
>
> Hello,
>
> I stumbled on this while trying to elisp a few things into my X
> clipboard manager. Evaluating these two expressions in turn:
>
> (gui-set-selection 'CLIPBOARD "1")
> (gui-set-selection 'CLIPBOARD "2")
>
> results in both "1" and "2" being saved to the clipboard history.
> However:
>
> (progn
>   (gui-set-selection 'CLIPBOARD "1")
>   (gui-set-selection 'CLIPBOARD "2"))
>
> results in "2" being saved to the clipboard history but, contrary to
> what I would expect, not "1". On the other hand this:
>
> (progn
>   (gui-set-selection 'CLIPBOARD "3")
>   (sleep-for 1)
>   (gui-set-selection 'CLIPBOARD "4"))
>
> gets both "3" and "4" onto the clipboard (history). I get similar
> results with kill-new in place of gui-set-selection 'CLIBOARD and with
> other ways of grouping the two kills into one expression.
>
> Why does waiting work around the problem?

Because it takes time for X clipboard managers to respond to selection
ownership changes and to complete reading from other programs'
selections.

Not a bug, sorry.

Message #17 received at 73830 <at> debbugs.gnu.org (full text, mbox):

From: snooze button <snooze-button <at> riseup.net>
To: Po Lu <luangruo <at> yahoo.com>
Cc: 73830 <at> debbugs.gnu.org
Subject: Re: bug#73830: using one expression to make multiple X selections
Date: Thu, 17 Oct 2024 13:29:38 +0200

[Message part 1 (text/plain, inline)]

On 17/10/2024 1:49, Po Lu wrote:
>> Why does waiting work around the problem?
> Because it takes time for X clipboard managers to respond to selection
> ownership changes and to complete reading from other programs'
> selections.
>
> Not a bug, sorry.

Thanks for the explanation, and no need to apologise!

For those of us wanting to read more on this, I dug around a bit and 
found some explanations

here https://github.com/jhunt/xclipd,

here https://jameshunt.us/writings/x11-clipboard-management-foibles/,

and here 
https://www.uninformativ.de/blog/postings/2017-04-02/0/POSTING-en.html

[Message part 2 (text/html, inline)]

Message #22 received at 73830-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: snooze button <snooze-button <at> riseup.net>
Cc: luangruo <at> yahoo.com, 73830-done <at> debbugs.gnu.org
Subject: Re: bug#73830: using one expression to make multiple X selections
Date: Sun, 27 Oct 2024 12:38:08 +0200

> Cc: 73830 <at> debbugs.gnu.org
> Date: Thu, 17 Oct 2024 13:29:38 +0200
> From: snooze button <snooze-button <at> riseup.net>
> 
> On 17/10/2024 1:49, Po Lu wrote:
> 
>  Why does waiting work around the problem?
> 
> Because it takes time for X clipboard managers to respond to selection
> ownership changes and to complete reading from other programs'
> selections.
> 
> Not a bug, sorry.
> 
> Thanks for the explanation, and no need to apologise!
> 
> For those of us wanting to read more on this, I dug around a bit and found some explanations
> 
> here https://github.com/jhunt/xclipd,
> 
> here https://jameshunt.us/writings/x11-clipboard-management-foibles/,
> 
> and here https://www.uninformativ.de/blog/postings/2017-04-02/0/POSTING-en.html

It sounds like there's nothing we can do here, so I'm now closing this
bug.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.