From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: akrl@sdf.org, stefan@marxist.se, 44743@debbugs.gnu.org
Subject: bug#44743: native-comp: confirm-exit-emacs warns about active processes when compiling
Date: Tue, 24 Nov 2020 17:42:40 +0200 [thread overview]
Message-ID: <83pn42u5fz.fsf@gnu.org> (raw)
In-Reply-To: <87eekj8a4t.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue, 24 Nov 2020 08:52:18 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Andrea Corallo <akrl@sdf.org>, stefan@marxist.se, 44743@debbugs.gnu.org
> Date: Tue, 24 Nov 2020 08:52:18 +0100
>
> Eli Zaretskii <eliz@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.
next prev parent reply other threads:[~2020-11-24 15:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 22:24 bug#44743: native-comp: confirm-exit-emacs warns about active processes when compiling Stefan Kangas
2020-11-20 8:35 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-20 11:35 ` Eli Zaretskii
2020-11-21 19:22 ` Stefan Kangas
2020-11-21 19:47 ` Eli Zaretskii
2020-11-21 20:35 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-24 7:52 ` Lars Ingebrigtsen
2020-11-24 15:42 ` Eli Zaretskii [this message]
2020-11-24 16:08 ` Stefan Kangas
2020-11-24 16:29 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-25 22:51 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-26 0:45 ` Stefan Kangas
2021-02-26 7:05 ` Eli Zaretskii
2021-02-26 13:02 ` Stefan Kangas
2021-02-26 13:44 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-26 14:12 ` Eli Zaretskii
2021-02-26 14:28 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-26 17:26 ` Stefan Kangas
2021-02-26 18:55 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-26 19:54 ` Eli Zaretskii
2021-02-26 20:31 ` Glenn Morris
2021-02-27 2:14 ` Stefan Kangas
2021-02-27 7:23 ` Eli Zaretskii
2020-11-24 16:36 ` Eli Zaretskii
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=83pn42u5fz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44743@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=larsi@gnus.org \
--cc=stefan@marxist.se \
/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).