From: "Peter Neilson" <neilson@windstream.net>
To: emacs-orgmode@gnu.org
Subject: Re: Tasks with lots of logbook entries are very slow
Date: Wed, 26 Mar 2014 04:31:51 -0400 [thread overview]
Message-ID: <op.xdblzdtvrns8nc@localhost.localdomain> (raw)
In-Reply-To: <lgu1vp$29j$1@ger.gmane.org>
On Wed, 26 Mar 2014 04:10:02 -0400, Pere Quintana Seguí
<pere@quintanasegui.com> wrote:
> El 25/03/14 19:27, Marcin Borkowski ha escrit:
>> Dnia 2014-03-25, o godz. 16:00:01
>> Pere Quintana Seguí <pere@quintanasegui.com> napisał(a):
>>
>>> I log most of my work with org-mode. Some of my tasks are repetitive,
>>> this is, I do them weekly or daily (i.e. empty mail inbox). After many
>>> years, the logs are very long. As a consequence, marking these tasks
>>> as done is *very* slow.
>>>
>>> Is there a workaround that does not involver deleting the logs?
>>
>> Archiving?
>>
>
> No, archiving would'nt work, as I need the task every day.
>
> Thanks for the tip.
>
> Pere
Perhaps this will help:
Standard method for log maintenance outside of org is to rotate logs into
archive. The current log is only for the current day (or month, week, or
year). Other criteria, such as log size, can be used to trigger rotation.
Rotation cuts off the current log, archives it, possibly deletes truly
ancient logs, and starts a new current log. Look up the Linux logrotate
command for further info. Here's one description:
http://www.thegeekstuff.com/2010/07/logrotate-examples/
next prev parent reply other threads:[~2014-03-26 8:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 15:00 Tasks with lots of logbook entries are very slow Pere Quintana Seguí
2014-03-25 18:27 ` Marcin Borkowski
2014-03-26 8:10 ` Pere Quintana Seguí
2014-03-26 8:31 ` Peter Neilson [this message]
2014-03-28 9:37 ` Pere Quintana Seguí
2014-03-29 14:06 ` Marcin Borkowski
2014-03-25 18:47 ` Achim Gratz
2014-03-26 8:12 ` Pere Quintana Seguí
2014-03-28 9:38 ` Pere Quintana Seguí
2014-03-26 10:41 ` Eric S Fraga
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=op.xdblzdtvrns8nc@localhost.localdomain \
--to=neilson@windstream.net \
--cc=emacs-orgmode@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.