[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#13566: 24.1; Too easy to forget things with remember

From: Sebastien Vauban
Subject: bug#13566: 24.1; Too easy to forget things with remember
Date: Tue, 14 May 2013 16:57:45 +0200
User-agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.3 (windows-nt)

Reuben Thomas wrote:
> On 14 May 2013 14:22, Sebastien Vauban <address@hidden> wrote:
>> Reuben Thomas wrote:
>>> On 14 May 2013 08:42, Glenn Morris <address@hidden> 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.
>> Please note that `remember' has been replaced by `org-capture', at least if
>> we speak of the same...
> I think you mean "superseded", not "replaced":

Yes, you're right.

> remember.el is still in Emacs bazaar. Yes, I'm aware of it, but presumably
> as long as remember.el is still included with Emacs it's acceptable to fix
> bugs in it? And since org-capture is not, as far as I know, based on
> remember, there is no reason to suspect that bugs in remember will be
> mirrored in org-capture?

I just wanted to direct you toward a better and more recent implementation.
But, sure, if you use the other one, and it's buggy, it should be fixed, as
long it's still around, in the official code base.

Best regards,

Sebastien Vauban

reply via email to

[Prev in Thread] Current Thread [Next in Thread]