From: Samuel Wales <email@example.com>
To: Ihor Radchenko <firstname.lastname@example.org>
Cc: email@example.com, David Masterson <firstname.lastname@example.org>
Subject: Re: archiving speed [was Re: Tips on maintaining history in Org Mode]
Date: Tue, 10 Aug 2021 18:08:03 -0700 [thread overview]
Message-ID: <CAJcAo8v3tB2OLo4X_Pcnci7kVAqxZYWzxGbRMxeVBJru_2ON5A@mail.gmail.com> (raw)
i have not bulk archived in a year or two, because it is too slow for
me. i am curious why, when appending to an archive file,
append-to-file or write-region are not used, to merely put the entries
there instead of loading the archive file into emacs?
[this is the case even with zero-size archive files; after a few
entries it slows down.]
On 2/28/21, Samuel Wales <email@example.com> wrote:
> thank you for your detaild reply.
> more below.
> On 2/28/21, Ihor Radchenko <firstname.lastname@example.org> wrote:
>> details why). So, many org commands tend to lag on large archives.
> that makes sense. but why would appending to an archive as the result
> of bulk archiving lag? if the problem is large archive files, which
> i'd bet is the case for a lot of users and not just me, then could org
> in principle be changed so that all it does is append? thus not lag?
> like, build the entry in a temporary buffer?
> as i see it, having more than one archive file per org file is good
> for speed, but doesn't work in existing org, because iirc e.g. v A in
> the agenda goes org agenda file -> corresponding archive file and will
> miss the archive files that do not have a corresponding org file with
> exactly the same basename sans extension.
> i'd be ok with released org either allowing hte user to make
> year-based archives by having all of org recognize them, or my just
> append thing above. maybe i am missing something.
>> The lags can be solved in several ways:
>> 1. Reduce the archive file size
> this implies to me e.g. year-based archives, which would fail the v A
> test iiuc. thus needed extra code.
>> 2. Use optimised folding mechanism  (this will speed up org-mode in
>> general as well)
> i look forward to this filtering down to maint. :] [i used to follow
> master but too much for me now for health reasons.]
>> 3. (untested) Put #+STARTUP: showeverything at the beginning of the
>> archives, so that nothing is going to be folded
> good idea. my included-by-agenda archive files do seem to be in
> showeveryting mode already for some reason. but perhaps not when bulk
> would it be a silly idea for an fr that org make this an option for
> bulk archiving? hmm or for archive files in general?
>>> i will keep in mind disabling font lock in archive files. any
>>> suggested code for that?
>> Note that it will mostly affect find-file performance. To disable
> if so, then i figure it's a one-time thing per file so no big deal.
> but thanks for hte font lock stuff i didnt' know about.
>> Sorry, the config is actually not yet formatted for public use. You can
>> search for the code block containing "defun
> firefox find does not seem to find it.
>> You will need that code block and the following code block.
>>  https://github.com/yantar92/org
> The Kafka Pandemic
> Please learn what misopathy is.
The Kafka Pandemic
Please learn what misopathy is.
next prev parent reply other threads:[~2021-08-11 1:08 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 [this message]
2021-08-11 4:13 ` Ihor Radchenko
2021-08-11 5:58 ` Samuel Wales
2021-08-11 6:43 ` Ihor Radchenko
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
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).