On 29/04/2021 21:12, Ihor Radchenko wrote:
There is org-outline-path-cache used by org-get-outline-cache. It avoids
computing parent's outline path multiple times, which is already a great
improvement.
Curiously my experience is that avoiding this lazy cache with 
backtracking and maintaining custom structure during sequential scan of 
the buffer works several times faster. However it is appropriate time to 
populate the cache you mentioned. Unfortunately it is still necessary to 
cleanup heading text, and it consumes significant time.
org-refile-cache can be simply let-bound to nil (in my case) or
alternative cache variable, if the alternative cache should persist.
Thank you for the idea. But I still hope that both function could use 
the same cache.

Reply via email to