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#46397: 27.1; Cannot delete buffer pointing to a file in a path that includes a file Date: Sat, 13 Feb 2021 10:07:44 +0200 Message-ID: <83h7mge6gf.fsf@gnu.org> References: <87h7mllgin.fsf@nexoid.at> <83a6scj745.fsf@gnu.org> <39d0e035-27b6-e2bd-daa2-747dda2c1a35@cs.ucla.edu> <835z2ziu52.fsf@gnu.org> <83pn15g28y.fsf@gnu.org> <2ce4897b-56ac-9409-b5e8-c735528e48f1@cs.ucla.edu> <83ft21frma.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="25458"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 46397@debbugs.gnu.org, eggert@cs.ucla.edu, craven@gmx.net To: Matt Armstrong Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Feb 13 09:08:09 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 1lApyL-0006X9-GJ for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 13 Feb 2021 09:08:09 +0100 Original-Received: from localhost ([::1]:59586 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lApyK-0000xZ-Bx for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 13 Feb 2021 03:08:08 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58406) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lApyE-0000xQ-V7 for bug-gnu-emacs@gnu.org; Sat, 13 Feb 2021 03:08:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:50195) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lApyE-00030z-O9 for bug-gnu-emacs@gnu.org; Sat, 13 Feb 2021 03:08:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lApyE-0002cY-JG for bug-gnu-emacs@gnu.org; Sat, 13 Feb 2021 03:08:02 -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, 13 Feb 2021 08:08: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.161320367510060 (code B ref 46397); Sat, 13 Feb 2021 08:08:02 +0000 Original-Received: (at 46397) by debbugs.gnu.org; 13 Feb 2021 08:07:55 +0000 Original-Received: from localhost ([127.0.0.1]:33508 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lApy6-0002cB-CU for submit@debbugs.gnu.org; Sat, 13 Feb 2021 03:07:55 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:40538) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lApy4-0002by-Ix for 46397@debbugs.gnu.org; Sat, 13 Feb 2021 03:07:52 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:45155) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lApxy-0002ss-4n; Sat, 13 Feb 2021 03:07:46 -0500 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:2520 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1lApxx-00045H-HK; Sat, 13 Feb 2021 03:07:45 -0500 In-Reply-To: (message from Matt Armstrong on Fri, 12 Feb 2021 15:59:40 -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:199900 Archived-At: > From: Matt Armstrong > Cc: 46397@debbugs.gnu.org, craven@gmx.net > Date: Fri, 12 Feb 2021 15:59:40 -0800 > > > Nobody owns the lock _now_, but how did that come to happen? We have > > no idea. It could be an indication that the user's files are under > > attack, for example. So silently assuming that the lock doesn't exist > > is not necessarily TRT. > > I think this portion of the discussion is on the fringe of the important > issue. For me, it _is_ the important issue. This bug is just an indication of a larger problem we have. > Right now, 'current_lock_owner' can return arbitrary errno > values, and if it does Emacs is in a bad situation: > > a) The user can't kill the buffer interactively. > b) Emacs can't exit, gets in a bad state, and must be killed. > > So, definitely, we need to fix that. So let's fix that instead of arguing, okay? > Separately, I continue to think Paul's recent commit is fine. I beg to differ: by solving that single aspect of a larger problem, it makes the larger problem less urgent, and that runs high risk of leaving it unsolved, IME.