From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 46935@debbugs.gnu.org
Subject: bug#46935: 28.0.50; Annoying interactions with X clipboard
Date: Tue, 09 Mar 2021 15:11:27 +0100 [thread overview]
Message-ID: <87lfawl8mo.fsf@gnus.org> (raw)
In-Reply-To: <878s6x9gjp.fsf@web.de> (Michael Heerdegen's message of "Tue, 09 Mar 2021 04:01:14 +0100")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Would it be appropriate and technically possible to implement a visual
> feedback like "waiting up to X seconds for feedback from whatever" or
> even a little countdown "waiting for feedback from system clipboard, 3,
> 2, 1, giving up" or so?
Looking at the code (it's receive_incremental_selection that does this
stuff, I guess?), it seems like it should be possible to implement
something like that in wait_for_property_change.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-03-09 14:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 23:28 bug#46935: 28.0.50; Annoying interactions with X clipboard Michael Heerdegen
2021-03-05 13:46 ` Lars Ingebrigtsen
2021-03-05 22:48 ` Michael Heerdegen
2021-03-06 12:33 ` Lars Ingebrigtsen
2021-03-07 0:03 ` Michael Heerdegen
2021-03-08 19:26 ` Lars Ingebrigtsen
2021-03-09 3:01 ` Michael Heerdegen
2021-03-09 14:11 ` Lars Ingebrigtsen [this message]
2021-03-10 2:10 ` Michael Heerdegen
2022-06-20 11:53 ` Lars Ingebrigtsen
2022-06-20 12:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20 15:34 ` Lars Ingebrigtsen
2022-06-22 12:46 ` Michael Heerdegen
2022-06-23 9:02 ` Lars Ingebrigtsen
[not found] ` <87y2f2m551.fsf@posteo.net>
2021-03-05 22:43 ` Michael Heerdegen
2021-03-06 2:55 ` Michael Heerdegen
2021-03-06 6:11 ` Thierry Volpiatto
2021-03-07 0:07 ` Michael Heerdegen
2021-03-07 6:07 ` 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
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=87lfawl8mo.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=46935@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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).