From: Robert Pluim <rpluim@gmail.com>
To: Saulius Menkevicius <sauliusmenkevicius@fastmail.com>
Cc: alan@idiocy.org, emacs-devel@gnu.org, p.stephani2@gmail.com,
matt@rfc20.org, Eli Zaretskii <eliz@gnu.org>,
mituharu@math.s.chiba-u.ac.jp
Subject: Re: master 2c79a8f 2/2: Use posix_spawn if possible.
Date: Tue, 08 Feb 2022 15:59:08 +0100 [thread overview]
Message-ID: <87leyl5rr7.fsf@gmail.com> (raw)
In-Reply-To: <b26d1ee2-05df-339a-792d-234cce948a56@fastmail.com> (Saulius Menkevicius's message of "Tue, 8 Feb 2022 14:18:43 +0200")
>>>>> On Tue, 8 Feb 2022 14:18:43 +0200, Saulius Menkevicius <sauliusmenkevicius@fastmail.com> said:
Saulius> I believe this is not a problem related to C#/dotnet but generally
Saulius> with how signals are blocked on child processes launched with
Saulius> posix_spawn in the current implementation.
(I could argue that if dotnet wants to ensure it receives SIGCHLD, it
should unblock it itself, but thatʼs a different discussion, we
definitely have an Emacs bug)
And come to think of it, the posix_spawn code path is only exercised
when not asking for a pseudo tty. Since the default value for
`process-connection-type' is t => pty, Iʼm assuming that the elisp
code in question is binding that to nil, or using the :connection-type
argument to `make-process'.
Would it be possible to test using ptys? If that works thatʼs a
workaround that requires no changes to emacs-28.
Thanks
Robert
--
next prev parent reply other threads:[~2022-02-08 14:59 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 6:48 master 2c79a8f 2/2: Use posix_spawn if possible Saulius Menkevicius
2022-01-25 8:41 ` Eli Zaretskii
2022-01-25 8:58 ` Saulius Menkevicius
2022-01-25 11:46 ` Jostein Kjønigsen
2022-01-25 11:55 ` Po Lu
2022-01-25 12:22 ` Eli Zaretskii
2022-01-25 12:25 ` Saulius Menkevicius
2022-01-25 13:47 ` Eli Zaretskii
2022-01-28 17:12 ` Matt Armstrong
2022-01-29 8:03 ` Saulius Menkevičius
2022-01-29 8:26 ` Eli Zaretskii
2022-01-31 20:48 ` Saulius Menkevicius
2022-02-01 9:59 ` Robert Pluim
2022-02-01 18:30 ` Saulius Menkevicius
2022-02-01 19:23 ` Robert Pluim
2022-02-01 19:52 ` Eli Zaretskii
2022-02-02 8:30 ` Robert Pluim
2022-02-02 8:54 ` Saulius Menkevičius
2022-02-07 21:12 ` Saulius Menkevicius
2022-02-08 8:27 ` Robert Pluim
2022-02-08 12:12 ` Eli Zaretskii
2022-02-08 12:18 ` Saulius Menkevicius
2022-02-08 14:59 ` Robert Pluim [this message]
2022-02-08 21:09 ` Saulius Menkevicius
2022-02-09 8:48 ` Robert Pluim
2022-02-12 8:44 ` Saulius Menkevicius
2022-02-12 8:59 ` Eli Zaretskii
2022-02-12 9:42 ` Saulius Menkevicius
2022-03-04 8:38 ` [PATCH] posix_spawn blocks SIGCHLD in spawned processes (was: Re: master 2c79a8f 2/2: Use posix_spawn if possible.) Jürgen Hötzel
2022-03-04 10:07 ` [PATCH] posix_spawn blocks SIGCHLD in spawned processes Robert Pluim
2022-03-04 15:41 ` Jürgen Hötzel
2022-03-04 16:08 ` Robert Pluim
2022-04-17 18:22 ` Philipp Stephani
2022-04-19 14:36 ` Robert Pluim
2022-04-19 14:48 ` Philipp Stephani
2022-04-19 16:07 ` Eli Zaretskii
2022-04-19 17:32 ` Robert Pluim
2022-04-04 14:13 ` Robert Pluim
2022-01-25 13:15 ` master 2c79a8f 2/2: Use posix_spawn if possible Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2021-11-08 11:00 Aaron Jensen
2021-11-08 11:03 ` Aaron Jensen
2021-11-08 19:37 ` Alan Third
2021-11-09 14:46 ` Philipp
2021-11-09 15:57 ` Aaron Jensen
2021-11-09 17:05 ` Eli Zaretskii
2021-11-09 18:12 ` Aaron Jensen
2021-11-12 11:48 ` Philipp
2021-11-12 13:42 ` Aaron Jensen
2021-11-12 22:05 ` Alan Third
2021-11-13 14:08 ` Aaron Jensen
2021-11-13 16:03 ` Philipp
2021-11-13 16:17 ` Aaron Jensen
2021-11-15 15:01 ` Dmitry Gutov
2020-12-25 13:16 Eli Zaretskii
2020-12-26 11:26 ` Philipp Stephani
2020-12-26 12:08 ` Eli Zaretskii
2020-12-26 12:16 ` Eli Zaretskii
2020-12-29 16:43 ` Philipp Stephani
2020-12-31 16:24 ` Philipp Stephani
2020-12-31 16:39 ` Eli Zaretskii
2020-12-31 17:36 ` Philipp Stephani
2020-12-31 17:47 ` Eli Zaretskii
2020-12-31 20:24 ` Philipp Stephani
2020-12-31 20:36 ` Eli Zaretskii
2021-01-01 7:59 ` martin rudalics
2021-01-01 8:04 ` Eli Zaretskii
2021-01-01 23:38 ` Andy Moreton
2021-01-01 23:56 ` Alan Third
2021-01-02 1:12 ` Andy Moreton
2021-01-02 6:53 ` Eli Zaretskii
2021-01-02 8:56 ` Andreas Schwab
2021-10-29 9:46 ` YAMAMOTO Mitsuharu
2021-10-30 18:30 ` Alan Third
2021-11-02 19:58 ` Alan Third
2021-11-02 20:15 ` Eli Zaretskii
2021-11-02 20:36 ` Alan Third
2021-11-03 3:24 ` Eli Zaretskii
2021-11-10 12:42 ` Philipp Stephani
2021-11-10 14:10 ` Eli Zaretskii
2021-11-11 17:52 ` Philipp
2021-11-11 18:00 ` Eli Zaretskii
2021-11-11 21:04 ` Philipp
2020-12-29 16:29 ` Philipp Stephani
2020-12-29 18:15 ` Eli Zaretskii
2020-12-29 21:36 ` Philipp Stephani
2020-12-30 3:33 ` Eli Zaretskii
2020-12-31 16:10 ` Philipp Stephani
2020-12-31 18:33 ` Eli Zaretskii
2020-12-31 17:50 ` Philipp Stephani
2020-12-31 18:34 ` Eli Zaretskii
2020-12-31 20:14 ` Philipp Stephani
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=87leyl5rr7.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=alan@idiocy.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=matt@rfc20.org \
--cc=mituharu@math.s.chiba-u.ac.jp \
--cc=p.stephani2@gmail.com \
--cc=sauliusmenkevicius@fastmail.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).