From: Maxim Nikulin <firstname.lastname@example.org> To: email@example.com Subject: Re: [PATCH] Bug: fragile org refile cache Date: Thu, 29 Apr 2021 19:45:50 +0700 Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <CAJcAo8vojXSFzQFKDp+gggqmPFCQpzTjY_-MTcJKgr4rpJWFXA@mail.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 . 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).
next prev parent reply other threads:[~2021-04-29 12:47 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-28 16:09 Maxim Nikulin 2021-04-29 0:50 ` Samuel Wales 2021-04-29 1:29 ` Ihor Radchenko 2021-04-29 1:34 ` Samuel Wales 2021-04-29 12:45 ` Maxim Nikulin [this message] 2021-04-29 14:12 ` Ihor Radchenko 2021-04-29 15:04 ` Maxim Nikulin 2021-04-29 16:08 ` Ihor Radchenko 2021-04-29 16:51 ` Maxim Nikulin 2021-04-30 16:56 ` Maxim Nikulin 2021-05-01 14:48 ` Maxim Nikulin 2021-05-02 6:59 ` Ihor Radchenko 2021-05-04 16:55 ` Maxim Nikulin 2021-05-05 0:53 ` Ihor Radchenko 2021-04-29 13:30 ` Ihor Radchenko 2021-04-29 19:17 ` Tim Cross 2021-04-29 22:43 ` Samuel Wales 2021-05-02 7:03 ` Ihor Radchenko
Reply instructions: 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: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://orgmode.org * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com' \ --firstname.lastname@example.org \ --email@example.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Org-mode mailing list This inbox may be cloned and mirrored by anyone: git clone --mirror https://orgmode.org/list/0 list/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 list list/ https://orgmode.org/list \ firstname.lastname@example.org public-inbox-index list Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.yhetil.org/yhetil.emacs.orgmode nntp://news.gmane.io/gmane.emacs.orgmode AGPL code for this site: git clone https://public-inbox.org/public-inbox.git