From: "Alan E. Davis" <email@example.com>
To: Carsten Dominik <firstname.lastname@example.org>
Cc: org-mode <email@example.com>
Subject: Re: a small remember suggestion
Date: Wed, 25 Mar 2009 00:22:31 +1000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2169 bytes --]
Wasn't going to say anything but at risk of sticking my foot in my mouth:
I learned that the convention for naming backups in Emacs is they end in ~.
Is it possible that if this is done, Emacs will automatically use the
mechanism that is available to keep a given number of old versions and a
given number of new versions? For example, I have this in my .emacs:
(setq kept-old-versions 2)
(setq kept-new-versions 4)
(setq delete-old-versions t)
"An inviscid theory of flow renders the screw useless, but the need for one
non-existent." ---Lord Raleigh (John William Strutt), or
else his son, who was also a scientist.
It is undesirable to believe a proposition when
there is no ground whatsoever for supposing it is true.
---- Bertrand Russell
On Tue, Mar 24, 2009 at 9:29 PM, Carsten Dominik <email@example.com>wrote:
> On Mar 24, 2009, at 4:29 AM, Samuel Wales wrote:
> On Sun, Mar 22, 2009 at 08:16, Carsten Dominik <firstname.lastname@example.org>
>>> I have now added a variable `org-remember-backup-directory'.
>>> Set this to a directory, and every remember buffer
>>> you create will end up in a separate file, with date
>>> and time in the file name, so that you can always recover.
>> That is perfect. Thank you.
>> Note that, if you use remember frequently, you will create
>>> a lot of these files. So maybe we need to think of an expiry
>>> mechanism? Like, remove any files older than a few days?
>> As one possibility, how about removing the file once the contents are
>> successfully moved to their target locations?
> Of course! I will do that.
>> After that,
>> (when (plusp number)
>> (message "you have %s saved remember files" number))
> Hmmm. When should this happen? Not after a
> successful remember process, I'd say.....
> - Carsten
>> Myalgic encephalomyelitis denialism is causing death (decades early;
>> Jason et al. 2006) and severe suffering (worse than nearly all other
>> diseases studied; e.g. Schweitzer et al. 1995) and grossly corrupting
>> science. http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm
[-- Attachment #1.2: Type: text/html, Size: 3602 bytes --]
[-- Attachment #2: Type: text/plain, Size: 204 bytes --]
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
next prev parent reply other threads:[~2009-03-24 14:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 19:28 a small remember suggestion Samuel Wales
[not found] ` <email@example.com>
2009-03-22 2:01 ` Alan E. Davis
2009-03-22 15:16 ` Carsten Dominik
2009-03-22 17:03 ` Richard Riley
2009-03-22 20:36 ` Alan E. Davis
2009-03-24 3:29 ` Samuel Wales
2009-03-24 3:42 ` Samuel Wales
2009-03-24 11:29 ` Carsten Dominik
2009-03-24 11:29 ` Carsten Dominik
2009-03-24 14:22 ` Alan E. Davis [this message]
2009-03-25 8:22 ` Carsten Dominik
2009-03-25 4:46 ` Samuel Wales
2009-03-25 6:24 ` Alan E. Davis
2009-03-25 8:23 ` Carsten Dominik
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).