From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rgm@gnu.org, 17036@debbugs.gnu.org, schwab@linux-m68k.org, rrt@sc3d.org
Subject: bug#17036: Continuation for Emacs: invoking a process on exit?
Date: Sun, 17 Apr 2022 14:49:23 +0200 [thread overview]
Message-ID: <87wnfn98oc.fsf@gnus.org> (raw)
In-Reply-To: <83wnfnyjkg.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 17 Apr 2022 15:34:55 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> . when kill-emacs is called with RESTART non-nil, the value of ARG
> is ignored; this should at least be documented;
Emacs doesn't exit, so I thought it would be self-evident that ARG
(which is all about the exit code) is ignored.
> . the exit status of the restarted Emacs is discarded, so it will
> not be available to the parent program, at least on MS-Windows,
> and also if execvp fails for some reason;
Again, Emacs doesn't exit, so...
> . the semantics of the file descriptors open in the original Emacs
> process is not clear to me: will they remain open in the restarted
> Emacs, if the original Emacs opened them without CLOEXEC?
I thought we opened all file descriptors with CLOEXEC? If not, that's a
bug, since we'd be leaking file descriptors to programs we start with
`call-process', for instance.
> . does the restarted Emacs belong to the same process group? should
> it?
I think so, and I guess so?
> . on MS-Windows, if any of the argv[] command-line arguments have
> embedded whitespace, the restarted Emacs will not get the same
> elements in its argv[] array, because the Windows API for starting
> processes accepts the command-line arguments as a single string
Sounds like we should just document that this doesn't work on Windows,
then.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-04-17 12:49 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 22:47 bug#17036: Continuation for Emacs: invoking a process on exit? Reuben Thomas
2014-03-18 22:52 ` Andreas Schwab
2014-03-18 22:56 ` Reuben Thomas
2014-03-19 6:27 ` Glenn Morris
2014-03-19 13:10 ` Stefan
2014-03-19 13:19 ` Reuben Thomas
2014-03-19 16:51 ` Eli Zaretskii
2014-03-19 21:14 ` Reuben Thomas
2014-03-20 3:45 ` Eli Zaretskii
2014-03-20 12:02 ` Reuben Thomas
2014-03-20 17:43 ` Eli Zaretskii
2014-03-20 23:10 ` Reuben Thomas
2014-03-21 7:53 ` Eli Zaretskii
2014-03-21 10:09 ` Reuben Thomas
2014-03-21 10:18 ` Reuben Thomas
2014-03-21 10:18 ` Eli Zaretskii
2014-03-21 10:25 ` Reuben Thomas
2022-04-17 11:38 ` Lars Ingebrigtsen
2022-04-17 11:56 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-17 11:57 ` Eli Zaretskii
2022-04-17 12:08 ` Lars Ingebrigtsen
2022-04-17 12:34 ` Eli Zaretskii
2022-04-17 12:41 ` Eli Zaretskii
2022-04-17 12:52 ` Lars Ingebrigtsen
2022-04-17 12:49 ` Lars Ingebrigtsen [this message]
2022-04-17 14:37 ` Eli Zaretskii
2022-04-17 14:49 ` Lars Ingebrigtsen
2022-04-17 15:51 ` Eli Zaretskii
2022-04-18 8:48 ` Lars Ingebrigtsen
2022-04-18 9:28 ` Eli Zaretskii
2022-04-17 14:29 ` Eli Zaretskii
2022-04-17 15:58 ` Eli Zaretskii
2022-04-17 16:02 ` Lars Ingebrigtsen
2022-04-17 17:49 ` Eli Zaretskii
2022-04-18 8:53 ` Lars Ingebrigtsen
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=87wnfn98oc.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=17036@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rgm@gnu.org \
--cc=rrt@sc3d.org \
--cc=schwab@linux-m68k.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).