Tim Cross <theophil...@gmail.com> writes: > I suspect the reason it is not done automatically is that getting that > right for all use cases is very hard to do without adding adverse impact > to performance. A cache which is marked as 'dirty' too often results in > too frequent cache refresh operations, but at the same time, determining > what changes in an org file actually invalidate the cache can be a > process intensive operation. Allowing the user to force cache refresh > when needed is likely a reasonable compromise.
Not really. `helm-org-ql' uses cache that is invalidated by _any_ change in buffer + updating cache only when results are queried. Performance is much better compared with built-in Org solutions. Also, there is `org-element-use-cache' doing more granular cache invalidation. You can enable it and test the performance. It is not really degraded (except some hard-to-catch bugs existing in the org-element-cache code). Best, Ihor
