From: Helmut Eller <eller.helmut@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 51177@debbugs.gnu.org
Subject: bug#51177: 29.0.50; stop-process on pipes
Date: Wed, 13 Oct 2021 16:04:18 +0200 [thread overview]
Message-ID: <m2h7dlggwt.fsf@gmail.com> (raw)
In-Reply-To: <83r1cpnknc.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 13 Oct 2021 16:01:43 +0300")
On Wed, Oct 13 2021, Eli Zaretskii wrote:
>> From: Helmut Eller <eller.helmut@gmail.com>
>> Date: Wed, 13 Oct 2021 11:20:01 +0200
>>
>>
>> I would like to request this feature: stop-process, when called with a
>> sub-process that is connected via pipes, should use delete_read_fd. It
>> should basically do the same as for sockets.
>
> Unlike with sockets, we are talking about a real sub-process on the
> other end of the pipe, and it will now get SIGPIPE. Are we sure this
> is OK? perhaps it will interfere with the process's cleanup when it
> receives a signal?
A valid concern, yes.
> If there's any real possibility this could change behavior, I think we
> should make such behavior optional.
Maybe we could add a pair of functions that exposes delete_read_fd and
add_process_read_fd more directly.
Helmut
next prev parent reply other threads:[~2021-10-13 14:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 9:20 bug#51177: 29.0.50; stop-process on pipes Helmut Eller
2021-10-13 11:45 ` Lars Ingebrigtsen
2021-10-13 13:39 ` Helmut Eller
2021-10-13 13:01 ` Eli Zaretskii
2021-10-13 14:04 ` Helmut Eller [this message]
2021-10-14 7:51 ` jakanakaevangeli
2021-10-14 8:00 ` Helmut Eller
2021-10-14 11:10 ` Lars Ingebrigtsen
2021-10-16 16:24 ` Helmut Eller
2021-10-16 16:47 ` Eli Zaretskii
2021-10-16 17:07 ` Helmut Eller
2021-10-18 6:58 ` Lars Ingebrigtsen
2021-11-11 19:47 ` Helmut Eller
2021-11-12 3:35 ` Lars Ingebrigtsen
2021-11-12 5:13 ` Helmut Eller
2021-11-12 6:30 ` Lars Ingebrigtsen
2021-11-12 7:21 ` Eli Zaretskii
2021-11-12 8:28 ` Helmut Eller
2021-11-12 12:00 ` Eli Zaretskii
2021-11-12 12:34 ` Helmut Eller
2021-11-12 13:05 ` Eli Zaretskii
2021-11-12 13:26 ` Helmut Eller
2021-11-12 12:58 ` Helmut Eller
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=m2h7dlggwt.fsf@gmail.com \
--to=eller.helmut@gmail.com \
--cc=51177@debbugs.gnu.org \
--cc=eliz@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).