From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#44743: native-comp: confirm-exit-emacs warns about active processes when compiling Date: Sat, 21 Nov 2020 21:47:48 +0200 Message-ID: <831rgmze3f.fsf@gnu.org> References: <83y2iwz2eq.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12851"; mail-complaints-to="usenet@ciao.gmane.io" Cc: akrl@sdf.org, 44743@debbugs.gnu.org To: Stefan Kangas Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Nov 21 20:54:54 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kgYyD-0003DQ-8f for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 21 Nov 2020 20:54:53 +0100 Original-Received: from localhost ([::1]:44214 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kgYyC-00060R-9v for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 21 Nov 2020 14:54:52 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36434) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kgYsY-0001J6-48 for bug-gnu-emacs@gnu.org; Sat, 21 Nov 2020 14:49:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:34676) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kgYsX-0006LL-Re for bug-gnu-emacs@gnu.org; Sat, 21 Nov 2020 14:49:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kgYsX-0003fq-QF for bug-gnu-emacs@gnu.org; Sat, 21 Nov 2020 14:49:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 21 Nov 2020 19:49:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 44743 X-GNU-PR-Package: emacs Original-Received: via spool by 44743-submit@debbugs.gnu.org id=B44743.160598809014059 (code B ref 44743); Sat, 21 Nov 2020 19:49:01 +0000 Original-Received: (at 44743) by debbugs.gnu.org; 21 Nov 2020 19:48:10 +0000 Original-Received: from localhost ([127.0.0.1]:46222 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kgYrh-0003eh-TV for submit@debbugs.gnu.org; Sat, 21 Nov 2020 14:48:10 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:36178) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kgYrf-0003eT-7j for 44743@debbugs.gnu.org; Sat, 21 Nov 2020 14:48:08 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:33966) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kgYrX-00061w-AF; Sat, 21 Nov 2020 14:48:00 -0500 Original-Received: from [176.228.60.248] (port=4342 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kgYrW-0006EX-JN; Sat, 21 Nov 2020 14:47:59 -0500 In-Reply-To: (message from Stefan Kangas on Sat, 21 Nov 2020 11:22:58 -0800) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:193815 Archived-At: > From: Stefan Kangas > Date: Sat, 21 Nov 2020 11:22:58 -0800 > Cc: 44743@debbugs.gnu.org > > > 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. I understand your opinion, but I don't think that's the only opinion that could exist. Caching the compiled modules can hardly be regarded as an implementation detail when compilation takes a tangible amount of time -- which is why we cache the results in the first place. IOW, if compilation is interrupted, Emacs will try to compile it again the next time, and the code will run slower than expected. So if this is an implementation detail, it will be acutely obvious to users, and they may wish to wait a bit with exiting Emacs to let the compilation run to the end. It is not unlike the case where you sent an email message and want to exit Emacs before the message transmission has ended. Users will appreciate a degree of control in these cases. > 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. I think interrupting compilation also comes with maintenance head-aches, such as the temporary files left behind, incomplete .eln files we'd need to clean up, etc. > 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. I think the argument is about what is "reasonable" here, all the rest is agreed upon.