|
From: | Paul Eggert |
Subject: | bug#46397: 27.1; Cannot delete buffer pointing to a file in a path that includes a file |
Date: | Fri, 19 Feb 2021 11:45:24 -0800 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 |
On 2/19/21 11:10 AM, Matt Armstrong wrote:
(a) Modify `kill-buffer' to call `unlock-buffer' sooner, closer to the point where it is already running hooks prompting the user. Handle unlock errors there by prompting.
How would unlock-buffer's API change, so that kill-buffer and unlock-buffer's other callers can do the right thing? Would it signal an error, and if so which one (or a new kind of error)?
[Prev in Thread] | Current Thread | [Next in Thread] |