From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Spencer Baugh <sbaugh@janestreet.com>
Cc: sbaugh@catern.com, 64423@debbugs.gnu.org
Subject: bug#64423: 29.0.92; save-interprogram-paste-before-kill doesn't prevent streaming large selections
Date: Thu, 06 Jul 2023 09:59:14 +0800 [thread overview]
Message-ID: <878rbtn6kt.fsf@yahoo.com> (raw)
In-Reply-To: <iery1jtj21x.fsf@janestreet.com> (Spencer Baugh's message of "Wed, 05 Jul 2023 20:50:34 -0400")
Spencer Baugh <sbaugh@janestreet.com> writes:
> And yet, we do this today: that's what x-selection-timeout does. Should
> we remove that functionality?
[...]
> I assume we should not remove that functionality. So if automatically
> interrupting a selection transfer if the owner takes too long is fine,
> what's the issue with interrupting it if the owner sends too much data?
Because sending a lot of data is *NOT* a bug in the selection owner.
Delaying subsequent user activity for a significant amount of time is.
> Both situations are usually the result of buggy X clients, both
> situations would break Emacs if not handled, both situations are
> standard considerations for robustness in any network protocol.
Blocking user interaction while quitting remains possible is not
``broken'' in my book.
> No, because then they are performing an operation which it makes sense
> might block: pasting data copied from another application. In that
> situation, they are fine with it.
[...]
> No, there is no problem with other X clients. It is simply that users
> expect delays when yanking and don't expect delays when killing.
>
> So, Emacs should be able to configure a different x-selection-timeout
> when running the save-interprogram-paste-before-kill logic, to reflect
> the fact that users have these different expectations for yanking and
> killing. I don't see why this is objectionable.
Taking more than five seconds to yank points to a bug in whichever
client is owning the clipboard selection at the time of the yank.
next prev parent reply other threads:[~2023-07-06 1:59 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 14:13 bug#64423: 29.0.92; save-interprogram-paste-before-kill doesn't prevent streaming large selections sbaugh
2023-07-03 2:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-03 12:46 ` Spencer Baugh
2023-07-04 0:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-04 1:45 ` sbaugh
2023-07-04 3:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-04 11:46 ` sbaugh
2023-07-04 13:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-04 14:46 ` sbaugh
2023-07-04 16:18 ` Eli Zaretskii
2023-07-04 16:32 ` Ihor Radchenko
2023-07-04 16:41 ` Eli Zaretskii
2023-07-04 16:48 ` sbaugh
2023-07-04 17:02 ` Eli Zaretskii
2023-07-04 17:14 ` Ihor Radchenko
2023-07-04 17:30 ` Eli Zaretskii
2023-07-04 17:35 ` Ihor Radchenko
2023-07-05 0:30 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-05 2:29 ` Eli Zaretskii
2023-07-05 3:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-05 11:27 ` Eli Zaretskii
2023-07-05 0:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-05 13:59 ` Spencer Baugh
2023-07-06 0:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-06 0:50 ` Spencer Baugh
2023-07-06 1:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-07-08 16:39 ` sbaugh
2023-07-08 16:48 ` Eli Zaretskii
2023-07-08 17:07 ` Spencer Baugh
2023-07-08 17:49 ` Eli Zaretskii
2023-07-09 0:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-09 6:10 ` Eli Zaretskii
2023-07-09 6:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-09 6:46 ` Eli Zaretskii
2023-07-12 19:18 ` sbaugh
2023-07-13 0:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-13 4:48 ` Eli Zaretskii
2023-07-13 16:17 ` sbaugh
2023-07-13 18:39 ` Eli Zaretskii
2023-07-13 22:39 ` sbaugh
2023-07-15 8:31 ` Eli Zaretskii
2023-07-15 8:33 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-15 9:01 ` Eli Zaretskii
2023-07-15 9:35 ` Eli Zaretskii
2023-07-15 17:38 ` sbaugh
2023-07-15 19:12 ` Eli Zaretskii
2023-07-15 21:00 ` Spencer Baugh
2023-07-17 16:43 ` Mattias Engdegård
2023-08-03 15:53 ` Spencer Baugh
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=878rbtn6kt.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=64423@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=sbaugh@catern.com \
--cc=sbaugh@janestreet.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 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).