all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 32000@debbugs.gnu.org, Brad Lindsay <sluggy.fan@gmail.com>
Subject: bug#32000: 26.1; Behavior of buffer-offer-save not lining up with documentation
Date: Sat, 12 Oct 2019 23:22:54 +0200	[thread overview]
Message-ID: <87k199irpt.fsf@gnus.org> (raw)
In-Reply-To: <87in62o59s.fsf@gmail.com> (Noam Postavsky's message of "Thu, 28 Jun 2018 19:33:35 -0400")

Noam Postavsky <npostavs@gmail.com> writes:

> Brad Lindsay <sluggy.fan@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





      parent reply	other threads:[~2019-10-12 21:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-28 22:56 bug#32000: 26.1; Behavior of buffer-offer-save not lining up with documentation Brad Lindsay
2018-06-28 23:33 ` Noam Postavsky
2018-06-29  0:41   ` Brad Lindsay
2019-10-12 21:22   ` Lars Ingebrigtsen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k199irpt.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=32000@debbugs.gnu.org \
    --cc=npostavs@gmail.com \
    --cc=sluggy.fan@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.