Samuel Wales writes:
> are there intereim workarounds like semi-automatically moving large
> logbook entries, or entire logbooks, to a task that says "was logbook
> for ..." and then archiving that task? or automatically archiving old
> logbook entries?
My largest logbook contains ~2.5k clock
are there intereim workarounds like semi-automatically moving large
logbook entries, or entire logbooks, to a task that says "was logbook
for ..." and then archiving that task? or automatically archiving old
logbook entries?
On 3/12/22, Ihor Radchenko wrote:
> "fr...@t-online.de" writes:
>
>>
"fr...@t-online.de" writes:
> I have just one headline and do a simple property search (prop1="blah1")
> for the 'org-agenda', but this takes about 10 seconds!
Thanks for providing a reproducible example! We know about this
performance issue. Performance has been improved in the development
> "fmd" == fr ml@t-online de writes:
fmd> I have just one headline and do a simple property search
fmd> (prop1="blah1") for the 'org-agenda', but this takes about 10
fmd> seconds!
Org versions from recent years don’t like large logbooks and don’t like
large files. For agenda,
Hello,
I have just one headline and do a simple property search (prop1="blah1")
for the 'org-agenda', but this takes about 10 seconds!
--- FILE:
* empty item but with a long logbook
:PROPERTIES:
:prop1: blah1
:END:
:LOGBOOK:
CLOCK: [2022-03-12 Sat 05:05]--[2022-03-12 Sat 05:24] => 0:19
