unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Reuben Thomas <rrt@sc3d.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 13566@debbugs.gnu.org
Subject: bug#13566: 24.1; Too easy to forget things with remember
Date: Tue, 14 May 2013 12:40:41 +0100	[thread overview]
Message-ID: <CAOnWdogjNEu-cwM0JPu0NK4=FaZSaA31Td8qaBDOa063WWY7qA@mail.gmail.com> (raw)
In-Reply-To: <764ne680tf.fsf@fencepost.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 963 bytes --]

On 14 May 2013 08:42, Glenn Morris <rgm@gnu.org> wrote:

> Reuben Thomas wrote:
>
> > The *Remember* buffer, as a non-file-visiting buffer, does not cause a
> > prompt when you kill it or exit Emacs with the contents unsaved. This is
> > unfortunate: I just lost 15 minutes' work when I hit C-x C-c in
> > remember-mode by mistake instead of C-c C-c.
> >
> > I can fix this particular problem by adding
> >
> > (lambda nil (setq buffer-offer-save t))
> >
> > to remember-mode-hook, but shouldn't this be the default behavior?
>
> Sounds right, please apply.
> Or maybe (I don't use remember) you want to add remember-finalize to
> kill-emacs-hook or kill-emacs-query-functions.
>

It seems to me that it's more consistent to make Emacs prompt to save the
remember buffer, as it does for other unsaved buffers (the alternative
suggested here would make Emacs silently save the remember buffer if
exited), but I'd appreciate some guidance.

-- 
http://rrt.sc3d.org

[-- Attachment #2: Type: text/html, Size: 1450 bytes --]

  reply	other threads:[~2013-05-14 11:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-27 17:43 bug#13566: 24.1; Too easy to forget things with remember Reuben Thomas
2013-05-14  7:42 ` Glenn Morris
2013-05-14 11:40   ` Reuben Thomas [this message]
2013-05-14 15:54     ` Glenn Morris
2013-05-14 16:05       ` Reuben Thomas
2013-05-14 16:14         ` Glenn Morris
2013-05-14 16:44           ` Reuben Thomas
2013-05-14 17:10             ` Glenn Morris
2013-05-14 18:10               ` Reuben Thomas
2013-05-14 19:53                 ` Reuben Thomas
2013-05-14 19:56                   ` Reuben Thomas
     [not found]   ` <mailman.25717.1368531694.855.bug-gnu-emacs@gnu.org>
     [not found]     ` <mailman.25717.1368531694.855.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2013-05-14 13:22       ` Sebastien Vauban
2013-05-14 13:27         ` Reuben Thomas
     [not found]         ` <mailman.25723.1368538120.855.bug-gnu-emacs@gnu.org>
     [not found]           ` <mailman.25723.1368538120.855.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2013-05-14 14:57             ` Sebastien Vauban
2013-05-14 15:00               ` Reuben Thomas
2013-05-14 15:12                 ` Sebastien Vauban
2013-10-17 23:08 ` bug#13566: Commit made Reuben Thomas
2013-10-18  1:18   ` Glenn Morris
2013-10-18  2:57   ` Stefan Monnier
2013-10-18  8:45     ` Reuben Thomas
2013-10-18 12:59       ` Stefan Monnier
2013-10-18 13:05         ` Reuben Thomas

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='CAOnWdogjNEu-cwM0JPu0NK4=FaZSaA31Td8qaBDOa063WWY7qA@mail.gmail.com' \
    --to=rrt@sc3d.org \
    --cc=13566@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).