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 <orgm...@adamspiers.org> 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. > > Cheers, > Adam > > -- The Kafka Pandemic What is misopathy? https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
