Re: [PATCH] Bug: fragile org refile cache

[Maxim Nikulin <manikulin@gmail.com>]

On 29/04/2021 08:29, Ihor Radchenko wrote:
> I do not observe the breakage as described in the first message,
> mostly because I use refile cache exclusively for org-refile.

Maybe I could avoid org-goto as well. Actual reason to use it was that 
it does not ask for file name as the first step in the case of 
(org-refile-use-outline-path 'file). It took enough time to me to 
realize how to jump/refile to non-leaf heading without such settings.

> A faster, more reliable, caching would
> be certainly welcome.

Just an idea. Is it possible to implement some specific text property 
for heading lines, namely cleaned out heading text (no cookies, tags, 
hidden parts of links), that is updated after each editing (likely 
something like font locks)? It could significantly speed up scanning 
buffer for goto/refile targets. Unfortunately it would not help for 
files that have not opened yet.

> I am aware at least about org-element, 
> org-scan-tags, org-agenda, org-refile, and org-goto.

To be clear, org-refile and org-goto share the same cache and it is the 
source of the problem.

> A good > implementation coming to my mind is org-ql [1].

I have not looked into the code yet, so I am not ready to discuss it. At 
least Adam should agree to submit patches to org and Bastien and Nicolas 
should agree to support it.

On 29/04/2021 08:34, Samuel Wales wrote:
> 
> would it be more useful if it automaticaly generated the cache instead
> of telling you to runt he command to do so?

I am surprised as well that cache is not just regenerated when 
org-refile detects that it is stale. Can it be that under certain 
circumstances it just causes delay and, even with updated cache, user 
action fails anyway?

On 29/04/2021 07:50, Samuel Wales wrote:
> i cannot reach the thread you point to, however.

Actually namely your response inspired me to look closer at the 
implementation of collection of refile targets. Is there a particular 
form of Message-Id that is convenient for you? The date of initial 
message is 2021-03-02 (in UTC).