From: Eli Zaretskii <eliz@gnu.org>
To: Spencer Baugh <sbaugh@janestreet.com>
Cc: luangruo@yahoo.com, 63865@debbugs.gnu.org
Subject: bug#63865: 29.0.90; call-process while owning the X selection hangs other processes
Date: Sat, 03 Jun 2023 18:50:11 +0300 [thread overview]
Message-ID: <831qis8s0c.fsf@gnu.org> (raw)
In-Reply-To: <ier5y84a7aj.fsf@janestreet.com> (message from Spencer Baugh on Sat, 03 Jun 2023 11:34:44 -0400)
> From: Spencer Baugh <sbaugh@janestreet.com>
> Cc: luangruo@yahoo.com, 63865@debbugs.gnu.org
> Date: Sat, 03 Jun 2023 11:34:44 -0400
>
> What about a new version of call-process, maybe
> "call-process-allow-lisp", which doesn't stop timers/process
> filters/Lisp/etc from running while Emacs is blocked in it? Then any
> caller which doesn't want to stop Lisp from running while they are
> waiting for the subprocess can use "call-process-allow-lisp" instead of
> "call-process".
If "Emacs is blocked", timers and process filters cannot run. So I'm
not sure I understand what you mean here.
if you mean to use start-process instead, then why exactly do we need
a new function? The building blocks for coding that are already
available, and I very much doubt that you will be able to come up with
one-fits-all combination of them anyway, because of the different
needs: what exactly should be blocked and what not, and how.
> I can implement that if it sounds desirable. I can also send a mail to
> emacs-devel if you want more discussion of it beforehand.
Yes, please. This discussion doesn't belong here.
next prev parent reply other threads:[~2023-06-03 15:50 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 [this message]
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
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=831qis8s0c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63865@debbugs.gnu.org \
--cc=luangruo@yahoo.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).