From: Samuel Wales <firstname.lastname@example.org>
To: Adam Spiers <email@example.com>
Cc: org-mode mailing list <firstname.lastname@example.org>
Subject: Re: make org-refile auto-recache when needed?
Date: Sun, 2 Aug 2020 13:32:15 -0700 [thread overview]
Message-ID: <CAJcAo8vGrTPSLhismQ2b2-d+ctYqsh_8vOj41v-u_w40=ZZxXA@mail.gmail.com> (raw)
i recall wanting this at some point also, and also did not figure out
why one would not want it.
perhaps it thinks you will use an alternate to refiling if you know it
will be too slow.
but it's worth keeping in mind that caching has, or had, bugs. in
particular, if refile targets are filtered [and you might have more
than one set], a single cache could seemingly get confused. of course
a solution would be to filter late.
if there is anything else that can be done to speed up refile and
refile goto /without/ caching, that's definitely best. you have
probably profiled, but make sure your completer [ivy, ido, helm] is
not the bottleneck. i wish we could get rid of this cache.
On 7/15/20, Adam Spiers <email@example.com> wrote:
> Hi all,
> I note that when org-refile-use-cache is enabled and the cache becomes
> stale, attempting to refile results in this error message (originating
> from `org-refile-check-position'):
> Invalid refile position, please clear the cache with `C-0 C-c C-w'
> before refiling
> Is there any reason why it couldn't just automatically rebuild the
> cache when needed? If it did that then I struggle to imagine why
> anyone would ever *not* want the cache enabled, because in the worst
> case org-refile would just behave the same as when the cache is
> disabled, and in the best case it would perform a lot faster.
The Kafka Pandemic
What is misopathy?
next prev parent reply other threads:[~2020-08-02 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 12:17 make org-refile auto-recache when needed? Adam Spiers
2020-08-02 8:48 ` Ihor Radchenko
2020-08-02 20:32 ` Samuel Wales [this message]
2020-09-04 14:12 ` Bastien
2020-09-05 16:20 ` Adam Spiers
2020-09-06 5:09 ` Bastien
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).