all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>, Andrea Corallo <akrl@sdf.org>
Cc: 44743@debbugs.gnu.org
Subject: bug#44743: native-comp: confirm-exit-emacs warns about active processes when compiling
Date: Sat, 21 Nov 2020 11:22:58 -0800	[thread overview]
Message-ID: <CADwFkm=hNcBx96LNBsog1tEB5AzZ+yeCtLMGwC+iQJHozmS=aA@mail.gmail.com> (raw)
In-Reply-To: <83y2iwz2eq.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> > Expected result: No prompt is shown.  The native-comp processes are
>> > recognized and killed automatically.
>>
>> I agree this would be nice to have.
>
> 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.

Compiling in the background should in my opinion work as transparently
as possible.  The fact that we cache compilation results should be
considered an implementation detail.  We don't need to shape our
outwardly behavior by such implementation details.

We could of course support what you suggest.  I'm not against it as an
option.  But I don't think it is very important, and it would take some
time and effort to implement and maintain.  I'm not sure that effort is
well-spent at this point, and would rather leave it for the future.

IOW, I think we should work on reasonable defaults first, and only add
options in later once we are sure that we really need them.





  reply	other threads:[~2020-11-21 19:22 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADwFkm=hNcBx96LNBsog1tEB5AzZ+yeCtLMGwC+iQJHozmS=aA@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=44743@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=eliz@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.