unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Spencer Baugh <sbaugh@janestreet.com>
To: 63865@debbugs.gnu.org
Subject: bug#63865: 29.0.90; call-process while owning the X selection hangs other processes
Date: Fri, 23 Jun 2023 10:26:53 -0400	[thread overview]
Message-ID: <iercz1muudu.fsf@janestreet.com> (raw)
In-Reply-To: <iermt1hs41u.fsf@igm-qws-u22796a.mail-host-address-is-not-set> (Spencer Baugh's message of "Fri, 02 Jun 2023 21:55:09 -0400")


BTW, the buggy behavior in Slack at least can be fixed by running:

slack 'slack://setting/?update={"isClipboardReadDisabled":true}'

then Slack won't constantly try to read the clipboard in the background.
(Apparently this may be fixed in the future, future readers should check
with Slack)

Though, I'm still of the opinion that we should make a
call-process-with-lisp which doesn't stop Lisp from running while
call-process-with-lisp is running, and use that everywhere.  Then we
wouldn't be triggering such bugs...





      parent reply	other threads:[~2023-06-23 14:26 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-03  1:55 bug#63865: 29.0.90; call-process while owning the X selection hangs other processes Spencer Baugh
2023-06-03  6:02 ` Eli Zaretskii
2023-06-03  7:11   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-03  9:12     ` Eli Zaretskii
2023-06-03  9:31       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-03 11:10     ` Spencer Baugh
2023-06-03 11:16       ` Eli Zaretskii
2023-06-03 12:07       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-03 12:30         ` Spencer Baugh
2023-06-03 12:55           ` Eli Zaretskii
2023-06-03 13:10             ` Spencer Baugh
2023-06-03 13:48               ` Eli Zaretskii
2023-06-03 14:12                 ` Spencer Baugh
2023-06-03 14:24                   ` Eli Zaretskii
2023-06-03 14:41                     ` Spencer Baugh
2023-06-03 15:02                       ` Eli Zaretskii
2023-06-03 15:34                         ` Spencer Baugh
2023-06-03 15:50                           ` Eli Zaretskii
2023-06-04  0:18                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-03 16:21               ` Andreas Schwab
2023-06-03 17:03                 ` Spencer Baugh
2023-06-03 17:07                   ` Eli Zaretskii
2023-06-04  0:15                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04  0:13               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04  0:12           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-23 14:26 ` Spencer Baugh [this message]

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=iercz1muudu.fsf@janestreet.com \
    --to=sbaugh@janestreet.com \
    --cc=63865@debbugs.gnu.org \
    /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).