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 17:44:24 +0100 [thread overview]
Message-ID: <CAOnWdogDp3XtorkKDx=s03tm3H3ibWZKszxKFWyCgwamEo3m5A@mail.gmail.com> (raw)
In-Reply-To: <e8ppwt5yiy.fsf@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
On 14 May 2013 17:14, Glenn Morris <rgm@gnu.org> wrote:
> Reuben Thomas wrote:
>
> > Auto-save protection would be nice, but that seems like a separate issue,
> > unless you're also suggesting that the prompt-on-exit for an unfinalized
> > remember buffer should be to save in a temporary file (which could be
> > confusing, especially for a user who doesn't use desktop.el or some other
> > session support), in which case I'm not sure it's a good idea.
>
> Maybe use write-contents-functions to make saving actually finalize.
>
Could you summarize what you're suggesting now, please? I previously
suggested one change, to add (setq buffer-offer-save t) to the function
"remember". Your suggestions taken together seem to involve multiple
changes to achieve a) the same result as mine and b) auto-save protection,
which seems worthwhile if it's similarly simple.
> It's a shame to see existing small functionality reimplemented by a
> mammoth package. But if no-one cares enough to do anything about it,
> that's how it is I suppose.
>
I'm not sure it makes a lot of difference if org-capture is as simple to
use, since org-mode is shipped as part of Emacs.
--
http://rrt.sc3d.org
[-- Attachment #2: Type: text/html, Size: 1928 bytes --]
next prev parent reply other threads:[~2013-05-14 16:44 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
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 [this message]
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='CAOnWdogDp3XtorkKDx=s03tm3H3ibWZKszxKFWyCgwamEo3m5A@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).