From: Stefan Kangas <stefan@marxist.se>
To: akrl@sdf.org, 44743@debbugs.gnu.org
Cc: larsi@gnus.org
Subject: bug#44743: native-comp: confirm-exit-emacs warns about active processes when compiling
Date: Thu, 25 Feb 2021 18:45:08 -0600 [thread overview]
Message-ID: <CADwFkm=g4QEfwTZWyXCnL2ka5TXw0dz38cC1Bc+m+OFbA3hGXQ@mail.gmail.com> (raw)
In-Reply-To: <xjfa6rrhicr.fsf@sdf.org>
Andrea Corallo <akrl@sdf.org> writes:
> IIUC this bug is "just" about deciding what's the best default behavior
> regarding requiring confirmation or not for killing running async
> compile processes when exiting Emacs.
>
> As my understanding is that Eli's preference is matching the current
> implementation (requiring it) I'm wondering if we can close this bug.
FWIW, I agree with your previous assessment that transparency by default
is the best choice here.
Ideally, nativecomp would not change how Emacs works in any user visible
way (besides better performance). But in practice, due to the way this
all works, there will necessarily have to be at least some differences.
The user visible change in behavior we discuss here is not necessary,
AFAIU, but completely avoidable. It feels to me like we leave our guts
hanging out on purpose.
next prev parent reply other threads:[~2021-02-26 0:45 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
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 [this message]
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='CADwFkm=g4QEfwTZWyXCnL2ka5TXw0dz38cC1Bc+m+OFbA3hGXQ@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=44743@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=larsi@gnus.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).