From: Andy Moreton <andrewjmoreton@gmail.com>
To: 46494@debbugs.gnu.org
Subject: bug#46494: 28.0.50; [native-comp] Problems with async background compile
Date: Sat, 20 Feb 2021 17:30:40 +0000 [thread overview]
Message-ID: <86y2fi7ikf.fsf@gmail.com> (raw)
In-Reply-To: <52dad420-fd72-fe1c-6f74-f4c114a2deb8@gmail.com>
On Sat 20 Feb 2021, Eli Zaretskii wrote:
>> From: Andy Moreton <andrewjmoreton@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
next prev parent reply other threads:[~2021-02-20 17:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 16:58 bug#46494: 28.0.50; [native-comp] Problems with async background compile Andy Moreton
2021-02-13 18:12 ` Eli Zaretskii
2021-02-13 20:20 ` Andy Moreton
2021-02-13 20:24 ` Eli Zaretskii
2021-02-14 8:01 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-14 15:31 ` Eli Zaretskii
2021-02-14 18:28 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-14 19:11 ` Eli Zaretskii
2021-02-20 10:37 ` Eli Zaretskii
2021-02-20 12:09 ` Andy Moreton
2021-02-20 12:54 ` Eli Zaretskii
2021-02-20 16:40 ` Andy Moreton
2021-02-20 16:54 ` Eli Zaretskii
2021-02-20 17:30 ` Andy Moreton [this message]
2021-02-20 17:37 ` Eli Zaretskii
2021-03-07 14:34 ` Eli Zaretskii
2021-03-08 0:19 ` Andy Moreton
2021-03-08 3:27 ` Eli Zaretskii
2021-02-21 21:22 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-22 3:28 ` Eli Zaretskii
2021-02-22 19:51 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-16 16:53 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-16 18:34 ` Eli Zaretskii
2021-03-16 20:10 ` Andy Moreton
2021-03-16 20:48 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=86y2fi7ikf.fsf@gmail.com \
--to=andrewjmoreton@gmail.com \
--cc=46494@debbugs.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).