GNU bug report logs -
#44743
native-comp: confirm-exit-emacs warns about active processes when compiling
Previous Next
Reported by: Stefan Kangas <stefan <at> marxist.se>
Date: Thu, 19 Nov 2020 22:25:02 UTC
Severity: minor
Done: Andrea Corallo <akrl <at> sdf.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
Stefan Kangas <stefan <at> marxist.se> writes:
> Eli Zaretskii <eliz <at> gnu.org> writes:
>
>>> From: Lars Ingebrigtsen <larsi <at> gnus.org>
>>> Cc: Andrea Corallo <akrl <at> sdf.org>, stefan <at> marxist.se, 44743 <at> debbugs.gnu.org
>>> Date: Tue, 24 Nov 2020 08:52:18 +0100
>>>
>>> Eli Zaretskii <eliz <at> gnu.org> writes:
>>>
>>> > FWIW, I think this should be controlled by a user option. It is not
>>> > at all obvious that everyone would like compilation processes to be
>>> > killed automatically, people might want to wait for them to complete.
>>>
>>> Since this is something that Emacs does automatically, in the
>>> background, I don't think a user option sounds like something somebody
>>> would want to tweak.
>>
>> IMO, we should offer an option precisely _because_ this is in
>> background, thus the user could be unaware of the compilation being
>> run. Since compilation takes non-negligible time, I envision users
>> who'd like to wait for a few moments if that gave them faster Lisp
>> next time.
>>
>> This is not unlike background subprocesses about which we do ask on
>> exit.
>
> IIUC, it's different from other background processes. The compilation
> will resume automatically the next time that file is loaded in
> subsequent invocations of Emacs.
Yes but you will loose the machine time invested into the compilation
that was aborted :) I guess 99% of people wouldn't care about it but
OTOH what's the downside of leaving a customize to control it?
Andrea
This bug report was last modified 4 years and 83 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.