GNU bug report logs - #32000
26.1; Behavior of buffer-offer-save not lining up with documentation

Previous Next

Full log

Message #14 received at 32000 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Noam Postavsky <npostavs <at> gmail.com>
Cc: 32000 <at> debbugs.gnu.org, Brad Lindsay <sluggy.fan <at> gmail.com>
Subject: Re: bug#32000: 26.1; Behavior of buffer-offer-save not lining up
 with documentation
Date: Sat, 12 Oct 2019 23:22:54 +0200

Noam Postavsky <npostavs <at> gmail.com> writes:

> Brad Lindsay <sluggy.fan <at> gmail.com> writes:
>
>> I am trying to create a function that creates a new empty buffer that
>> prompts you to save it when you kill it. Reading through the
>> documentation, it looks like I need to set “buffer-offer-save” to a
>> non-nil value since the new buffer is not a file-visiting buffer. I
>> have tried doing that, and verifying that the variable isn’t set and
>> that the new buffer isn’t empty, but when I close (kill) the buffer, I
>> don’t get a prompt.
>
> buffer-offer-save is for killing Emacs or save-some-buffers, to catch
> buffer killing use kill-buffer-query-functions.  We could probably make
> the docs a bit more explicit about this.

Looks like the doc string here was fixed a couple of days after this was
reported, so I'm closing the bug report now.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.