[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#46397: 27.1; Cannot delete buffer pointing to a file in a path that
From: |
Matt Armstrong |
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 |
Eli Zaretskii <eliz@gnu.org> 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.
bug#46397: 27.1; Cannot delete buffer pointing to a file in a path that includes a file, Bill Wohler, 2021/03/14