From: E Sabof <esabof@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 14512@debbugs.gnu.org
Subject: bug#14512: 24,3; buffer-offer-save doesn't seem to have any effect
Date: Fri, 31 May 2013 01:17:27 +0100 [thread overview]
Message-ID: <CAEp6DyaXK4CionarDuCzL4M0iPbu8xYhw-o-hq2qBrA+2PwNGw@mail.gmail.com> (raw)
In-Reply-To: <gx61y0dpyy.fsf@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
I no longer use it much, since I create/kill temporary buffers quite often.
But this is the default behavior in most programs, and I suspect many
people would want to change it. My 1 year ago self included.
On second thought, there might be a case for prompting for save only on
emacs exit, but I think it would be more natural if there was a separate
switch to do that, and it was responsible for all
(and (buffer-modified-p)
(or (buffer-file-name)
buffer-offer-save))
buffers.
On a related note, I get the impression that the prompt being hard coded is
a remnant from times when kill-buffer-query-functions didn't exist.
Evgeni
On Fri, May 31, 2013 at 12:09 AM, Glenn Morris <rgm@gnu.org> wrote:
>
> If you want Emacs to
>
> 1) offer to save a buffer on exit
> 2) offer to save a buffer on C-x k
>
> then why not simply make that buffer visit a file?
>
> Because you also probably want
>
> 3) some kind of auto-save in case your computer dies while you are
> editing the buffer
>
[-- Attachment #2: Type: text/html, Size: 1512 bytes --]
next prev parent reply other threads:[~2013-05-31 0:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 13:18 bug#14512: 24,3; buffer-offer-save doesn't seem to have any effect E Sabof
2013-05-30 14:05 ` Kevin Rodgers
2013-05-30 14:43 ` E Sabof
2013-05-30 18:10 ` Michael Heerdegen
2013-05-30 18:41 ` E Sabof
2013-05-30 23:09 ` Glenn Morris
2013-05-30 23:12 ` Glenn Morris
2013-05-31 0:17 ` E Sabof [this message]
2022-02-05 23:41 ` bug#14512: buffer-offer-save does not affect kill-buffer Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEp6DyaXK4CionarDuCzL4M0iPbu8xYhw-o-hq2qBrA+2PwNGw@mail.gmail.com \
--to=esabof@gmail.com \
--cc=14512@debbugs.gnu.org \
--cc=rgm@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).