From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Matt Armstrong Newsgroups: gmane.emacs.bugs Subject: bug#46397: 27.1; Cannot delete buffer pointing to a file in a path that includes a file Date: Sat, 13 Feb 2021 16:49:43 -0800 Message-ID: References: <87h7mllgin.fsf@nexoid.at> <83a6scj745.fsf@gnu.org> <39d0e035-27b6-e2bd-daa2-747dda2c1a35@cs.ucla.edu> <83tuqhg3j9.fsf@gnu.org> <83czx4e5h5.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="17252"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 46397@debbugs.gnu.org, eggert@cs.ucla.edu, craven@gmx.net To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Feb 14 01:50:13 2021 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 1lB5c5-0004Pe-M2 for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 14 Feb 2021 01:50:13 +0100 Original-Received: from localhost ([::1]:33542 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lB5c4-0000UI-Ns for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 13 Feb 2021 19:50:12 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44642) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lB5bu-0000U3-LJ for bug-gnu-emacs@gnu.org; Sat, 13 Feb 2021 19:50:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:51940) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lB5bu-0001uh-E4 for bug-gnu-emacs@gnu.org; Sat, 13 Feb 2021 19:50:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lB5bu-0002HF-CB for bug-gnu-emacs@gnu.org; Sat, 13 Feb 2021 19:50:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Matt Armstrong Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 14 Feb 2021 00:50:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 46397 X-GNU-PR-Package: emacs Original-Received: via spool by 46397-submit@debbugs.gnu.org id=B46397.16132637988738 (code B ref 46397); Sun, 14 Feb 2021 00:50:02 +0000 Original-Received: (at 46397) by debbugs.gnu.org; 14 Feb 2021 00:49:58 +0000 Original-Received: from localhost ([127.0.0.1]:35253 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lB5bp-0002Gs-Vk for submit@debbugs.gnu.org; Sat, 13 Feb 2021 19:49:58 -0500 Original-Received: from relay2-d.mail.gandi.net ([217.70.183.194]:57171) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lB5bo-0002GX-Do for 46397@debbugs.gnu.org; Sat, 13 Feb 2021 19:49:57 -0500 X-Originating-IP: 24.113.169.116 Original-Received: from matts-mbp-2016.lan (24-113-169-116.wavecable.com [24.113.169.116]) (Authenticated sender: matt@rfc20.org) by relay2-d.mail.gandi.net (Postfix) with ESMTPSA id AAA1840003; Sun, 14 Feb 2021 00:49:47 +0000 (UTC) In-Reply-To: <83czx4e5h5.fsf@gnu.org> 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:199973 Archived-At: Eli Zaretskii writes: >> There is also the case where 'kill_emacs' is called from a signal, >> which [...] > But we do ask about auto-save errors in these cases, don't we? If so, > why not ask about locks as well? I think auto-save issues messages and warnings, but never prompts ("asks about"). Auto save can call `display-warning' (see auto_save_error in fileio.c) or `message' (see message1() and message_with_string() calls in same). I can't find any prompts. So let's settle a question before going further. Would you be okay if lock errors were reported in the same way(s) auto-save errors are? I should reveal: during shut down, both `message' and `display-warning' seems to have no effect. The first thing `shut_down_emacs()' does is inhibit display, which is probably why. Taking this approach would be a tremendous simplification over what I had been thiking you were asking for. Most of my confusion centers around re-aranging code flow such that all possible errors occur, by construction, only *before* shut_down_emacs() may be called.