From: Bernt Hansen <email@example.com>
To: Bastien <firstname.lastname@example.org>
Cc: Loris Bennett <email@example.com>, firstname.lastname@example.org
Subject: Re: Archiving drawers?
Date: Sun, 26 Aug 2012 11:20:32 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Bastien's message of "Fri, 24 Aug 2012 14:34:02 +0200")
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 :)
When my LOGBOOK entries get too big I clone the task, remove the
repeater and mark it DONE (so I can archive the old entries and continue
with my current stuff)
For habits I keep some history so the current habit graph is correct
and for non-habits I usually (but not always) archive the clock entries
from beginning of this month and earlier.
My trigger for doing this is when I notice todo state changes take a
noticeable amount of time on the agenda. I do this infrequently so I
haven't bothered automating it. I do have to manually delete all of the
duplicated notes in the LOGBOOK drawer for the clone (clock lines are
removed in cloned tasks but the notes are not which feels wrong ... but
it hasn't bothered me enough to try to fix it yet.)
I'm sure there's a better way I haven't discovered yet.
Just my 2 cents.
prev parent reply other threads:[~2012-08-26 15:20 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
2012-08-24 19:10 ` Achim Gratz
2012-08-26 15:20 ` Bernt Hansen [this message]
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).