From: Bastien <firstname.lastname@example.org>
To: Loris Bennett <email@example.com>
Subject: Re: Archiving drawers?
Date: Fri, 24 Aug 2012 16:56:34 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Loris Bennett's message of "Fri, 24 Aug 2012 14:52:28 +0200")
"Loris Bennett" <firstname.lastname@example.org> writes:
> Bastien <email@example.com> writes:
>> Hi Loris,
>> "Loris Bennett" <firstname.lastname@example.org> writes:
>>> I have a small number of tasks that I clock into daily. I have already
>>> manually split off the older log entries into a separate draw called
>>> OLDLOGS. However, I was wondering whether there is a way of archiving
>>> these log entries while preserving the heading itself in the original
>>> org file.
>> The question is: _where_ to archive those log entries?
>> The best idea I can think of is another drawer, like you did.
>> As for automating this a bit, a nice Elisp exercise :)
> I was thinking more along the lines of the way archiving works already,
> but instead of moving the whole heading, a copy of the heading plus the
> old logs would be made in the archive file, and the old logs would be
> deleted from the original file, i.e.
But then archiving the "* Make tea" headline would require to merge the
logs of the archived one and those of the alive one. Quite some work.
next prev parent reply other threads:[~2012-08-24 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 12:19 Archiving drawers? Loris Bennett
2012-08-24 12:34 ` Bastien
2012-08-24 12:52 ` Loris Bennett
2012-08-24 14:56 ` Bastien [this message]
2012-08-24 19:10 ` Achim Gratz
2012-08-26 15:20 ` Bernt Hansen
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).