From: Ihor Radchenko <yantar92@gmail.com>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org, David Masterson <dsmasterson92630@outlook.com>
Subject: Re: archiving speed [was Re: Tips on maintaining history in Org Mode]
Date: Wed, 11 Aug 2021 14:43:51 +0800 [thread overview]
Message-ID: <87tujw8orc.fsf@localhost> (raw)
In-Reply-To: <CAJcAo8uMYUhZZrwYDJguEt5FM79w-68UA6n9=0s=ETg1o-OEkg@mail.gmail.com>
Samuel Wales <samologist@gmail.com> writes:
> i should clarify. bulk archiving slows down even with /nonexistent/
> (have not tried empty) archives. as part of normal and expected
> operation, bulk creates the archive for the first entry, and then
> subsequent entries are added. those get slower and slower.
That's what I suspected. I also see this and my suggestion helped
archiving speed in my case.
> i use (olpath category itags). i will try (file time) when i can, if
> that still applies. my brain needs to be more operational.
When you use category, every time you modify the original file (not the
archive!), Org mode re-calculates *all* the categories in the original
Org file. It happens for every single archived heading. If your original
Org file is large, re-calculations make things extremely slow.
Best,
Ihor
next prev parent reply other threads:[~2021-08-11 6:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 4:22 archiving speed [was Re: Tips on maintaining history in Org Mode] Samuel Wales
2021-03-01 6:02 ` Ihor Radchenko
2021-08-11 1:08 ` Samuel Wales
2021-08-11 4:13 ` Ihor Radchenko
2021-08-11 5:58 ` Samuel Wales
2021-08-11 6:43 ` Ihor Radchenko [this message]
2021-08-11 22:23 ` Samuel Wales
2021-08-12 0:24 ` Ihor Radchenko
2021-08-12 5:47 ` Samuel Wales
2021-08-12 3:38 ` Tim Cross
2021-08-12 5:49 ` Samuel Wales
2021-08-12 5:56 ` Tim Cross
2021-10-17 12:08 ` Ihor Radchenko
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=87tujw8orc.fsf@localhost \
--to=yantar92@gmail.com \
--cc=dsmasterson92630@outlook.com \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@gmail.com \
/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.