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: Wed, 17 Mar 2021 16:49:27 -0700 Message-ID: <87pmzx1gu0.fsf@rfc20.org> References: <87wnuio0ah.fsf@mdeb> <83h7lhn4he.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="31194"; 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 Thu Mar 18 00:50: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 1lMfvV-0007zv-3Y for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 18 Mar 2021 00:50:09 +0100 Original-Received: from localhost ([::1]:50576 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lMfvT-0003Ax-Li for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 17 Mar 2021 19:50:07 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51122) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lMfvO-0003Ap-1H for bug-gnu-emacs@gnu.org; Wed, 17 Mar 2021 19:50:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:32871) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lMfvN-0000p5-Pj for bug-gnu-emacs@gnu.org; Wed, 17 Mar 2021 19:50:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lMfvN-0001wU-M9 for bug-gnu-emacs@gnu.org; Wed, 17 Mar 2021 19:50:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Matt Armstrong Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 17 Mar 2021 23:50:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 46397 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 46397-submit@debbugs.gnu.org id=B46397.16160249827418 (code B ref 46397); Wed, 17 Mar 2021 23:50:01 +0000 Original-Received: (at 46397) by debbugs.gnu.org; 17 Mar 2021 23:49:42 +0000 Original-Received: from localhost ([127.0.0.1]:44417 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lMfv3-0001vY-T5 for submit@debbugs.gnu.org; Wed, 17 Mar 2021 19:49:42 -0400 Original-Received: from relay12.mail.gandi.net ([217.70.178.232]:47877) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lMfv1-0001vG-27 for 46397@debbugs.gnu.org; Wed, 17 Mar 2021 19:49:40 -0400 Original-Received: from mdeb (24-113-169-116.wavecable.com [24.113.169.116]) (Authenticated sender: matt@rfc20.org) by relay12.mail.gandi.net (Postfix) with ESMTPSA id 077B4200002; Wed, 17 Mar 2021 23:49:31 +0000 (UTC) Original-Received: from matt by mdeb with local (Exim 4.94) (envelope-from ) id 1lMfup-0009yC-P8; Wed, 17 Mar 2021 16:49:27 -0700 In-Reply-To: <83h7lhn4he.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:202542 Archived-At: Eli Zaretskii writes: > Thanks, I have just two minor comments: > > . I'd prefer a slightly different warning text, see below > . We need this change to be reflected in NEWS and perhaps in the manual Thank you for the review Eli. I've incorporated your feedback in the attached patches. I made the warning message even more terse than you suggested because before doing so the warnings looked like this: Warning (unlock-file): Error unlocking file Unlocking file: Permission denied, /tmp/inaccessible/foo, ignored [Disable showing] [Disable logging] ...which says "unlock file" too many times. With the current patch it is a little bit better: Warning (unlock-file): Unlocking file: Permission denied, /tmp/inaccessible/foo, ignored [Disable showing] [Disable logging] The "Unlocking file: Permission denied, /tmp/inaccessible/foo" is a form all `file-error' conditions have. Most relevant here is the "Unlocking file" prefix, which the C level API that generates these errors makes difficult to omit.