GNU bug report logs -
#46494
28.0.50; [native-comp] Problems with async background compile
Previous Next
Reported by: Andy Moreton <andrewjmoreton <at> gmail.com>
Date: Sat, 13 Feb 2021 16:59:02 UTC
Severity: normal
Found in version 28.0.50
Done: Andrea Corallo <akrl <at> sdf.org>
Bug is archived. No further changes may be made.
Full log
Message #44 received at submit <at> debbugs.gnu.org (full text, mbox):
On Sat 20 Feb 2021, Eli Zaretskii wrote:
>> From: Andy Moreton <andrewjmoreton <at> gmail.com>
>> Date: Sat, 20 Feb 2021 16:40:38 +0000
>>
>> Using "(w32-start-process-share-console t)" with 'SIGHUP seemed to work
>> without triggering the abort dialog, and killing emacs with async
>> processes running also did, not trigger the aborts.
>
> Great, thanks for trying this. So at the very least we have a
> workaround, if not the solution.
Yes. It also seemed faster, in that I had to be quicker at entering
process IDs to send a single before the subprocess exited normally.
> FTR, setting w32-start-process-share-console non-nil causes the
> subprocess to start a new process group, and sending SIGHUP to the
> inferior Emacs then kills it via the TerminateProcess API, whereas
> when w32-start-process-share-console is nil (the default), we try
> being nice, and send it the WM_CLOSE message.
If being polite does not work, then we will need the more forceful
approach.
AndyM
This bug report was last modified 4 years and 69 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.