From: "Ludovic Courtès" <ludo@gnu.org>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: Mikael Djurfeldt <mikael@djurfeldt.com>,
70144-done@debbugs.gnu.org, Christopher Baines <mail@cbaines.net>
Subject: bug#70144: system* affects signal handlers
Date: Mon, 06 May 2024 12:00:34 +0200 [thread overview]
Message-ID: <87msp3l0ot.fsf@gnu.org> (raw)
In-Reply-To: <871q6g5hz1.fsf@jpoiret.xyz> (Josselin Poiret's message of "Sun, 05 May 2024 18:41:38 +0200")
Hi,
Josselin Poiret <dev@jpoiret.xyz> skribis:
> Yes, I believe this is all taken care of by our use of posix_spawn
> (which was the point in the first place :) ).
Yup! I pushed the fix as 4ae33f76d6b33ea0bedfa36050d44c88d08c2823.
Thanks,
Ludo’.
prev parent reply other threads:[~2024-05-06 10:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 14:22 bug#70144: system* affects signal handlers Christopher Baines
2024-04-03 8:28 ` Mikael Djurfeldt
2024-05-02 14:17 ` Ludovic Courtès
2024-05-05 16:41 ` Josselin Poiret via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2024-05-06 10:00 ` Ludovic Courtès [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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87msp3l0ot.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=70144-done@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=mail@cbaines.net \
--cc=mikael@djurfeldt.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.
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).