GNU bug report logs - #17036
Continuation for Emacs: invoking a process on exit?

Previous Next

Package: emacs;

Reported by: Reuben Thomas <rrt <at> sc3d.org>

Date: Tue, 18 Mar 2014 22:48:01 UTC

Severity: wishlist

Fixed in version 29.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #94 received at 17036 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: larsi <at> gnus.org
Cc: rgm <at> gnu.org, schwab <at> linux-m68k.org, 17036 <at> debbugs.gnu.org, rrt <at> sc3d.org
Subject: Re: bug#17036: Continuation for Emacs: invoking a process on exit?
Date: Sun, 17 Apr 2022 18:58:05 +0300
> Date: Sun, 17 Apr 2022 17:29:20 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
> Cc: rgm <at> gnu.org, 17036 <at> debbugs.gnu.org, schwab <at> linux-m68k.org, rrt <at> sc3d.org
> 
> I eventually had an implementation idea that is much simpler than the
> above, so I went ahead and implemented it.  It currently doesn't work
> in a -nw session, I hope to debug that later.

The problems in the -nw session have something top do with the parent
releasing the console device and the restarted child attaching to it;
I'm unable to get that to work (not really surprising, as I know very
little about the subtleties of the Windows console sharing).  So for
now I just made restart-emacs fail in the -nw case on MS-Windows.

Btw, calling 'error' in this place, which we also do on Posix
platforms, is not very useful: this is past the call to
shut_down_emacs, so all 'error' does at this point is exit with an
error status, and the error message is lost.  Something to keep in
mind, I guess.




This bug report was last modified 3 years and 39 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.