From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#44743: native-comp: confirm-exit-emacs warns about active processes when compiling Date: Sat, 21 Nov 2020 20:35:03 +0000 Message-ID: References: <83y2iwz2eq.fsf@gnu.org> <831rgmze3f.fsf@gnu.org> Reply-To: Andrea Corallo Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26597"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Stefan Kangas , 44743@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Nov 21 21:36:11 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 1kgZcA-0006na-Sf for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 21 Nov 2020 21:36:10 +0100 Original-Received: from localhost ([::1]:54452 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kgZc9-0001Tc-AQ for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 21 Nov 2020 15:36:09 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44154) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kgZc2-0001TR-En for bug-gnu-emacs@gnu.org; Sat, 21 Nov 2020 15:36:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:34711) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kgZc2-0005p5-7i for bug-gnu-emacs@gnu.org; Sat, 21 Nov 2020 15:36:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kgZc2-0004ni-4W for bug-gnu-emacs@gnu.org; Sat, 21 Nov 2020 15:36:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Andrea Corallo Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 21 Nov 2020 20:36:02 +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.160599091018385 (code B ref 44743); Sat, 21 Nov 2020 20:36:02 +0000 Original-Received: (at 44743) by debbugs.gnu.org; 21 Nov 2020 20:35:10 +0000 Original-Received: from localhost ([127.0.0.1]:46256 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kgZbC-0004mS-8P for submit@debbugs.gnu.org; Sat, 21 Nov 2020 15:35:10 -0500 Original-Received: from mx.sdf.org ([205.166.94.24]:59292) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kgZb8-0004mE-M7 for 44743@debbugs.gnu.org; Sat, 21 Nov 2020 15:35:08 -0500 Original-Received: from mab (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTP id 0ALKZ3iq015004; Sat, 21 Nov 2020 20:35:03 GMT In-Reply-To: <831rgmze3f.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 21 Nov 2020 21:47:48 +0200") 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:193821 Archived-At: Eli Zaretskii writes: >> 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. I also think this option should be controlled by a customize. I can picture most "power users" legitimately willing to be informed of these processes being killed if present at exit. OTOH I guess the majority of non "power users" would like just to close Emacs transparently. Because of this my idea I think I'm for the transparent behavior as default. Andrea