From: Jack Kamm <jackkamm@tatersworld.org>
To: emacs-orgmode@gnu.org
Subject: Bug? org-id-find not finding some IDs
Date: Mon, 01 Aug 2022 18:45:37 -0700 [thread overview]
Message-ID: <87r11zifjy.fsf@gmail.com> (raw)
Hello,
The documentation for org-id-extra-files suggests that org-id-find
should search in Org files visited by Emacs:
> When Org reparses files to remake the list of files and IDs it is
> tracking, it will normally scan the agenda files, the archives
> related to agenda files, ... and any Org file currently visited by
> Emacs.
But, I've found that's not true, or maybe I'm misunderstanding the
doc.
For a minimal example, put the following in test.org:
> * Headline 1
> :PROPERTIES:
> :ID: b1569c92-3872-4ab9-80eb-274c4950991e
> :END:
Then:
1. emacs -Q test.org
2. C-x b *scratch*
3. M-: (org-id-find "b1569c92-3872-4ab9-80eb-274c4950991e")
Which returns nil. Also, "C-h v org-id-files" doesn't contain
test.org.
Or maybe the docstring for org-id-extra-files should be rewritten to
say "the current buffer" instead of "any Org file currently visited"?
Also, this seems to be the cause of this bug in org-caldav, which is
how I ran into it:
https://github.com/dengste/org-caldav/issues/230
Would there a recommended mitigation for this on org-caldav's side? I'm
thinking it could call
(org-id-update-id-locations org-caldav-files)
early on, to make sure org-caldav-files ends up in org-id-files.
Tested on following versions:
GNU Emacs 28.1 (build 2, x86_64-pc-linux-gnu, X toolkit, cairo version 1.17.6, Xaw3d scroll bars) of 2022-07-10
Org mode version 9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/share/emacs/28.1/lisp/org/)
Org mode version 9.5.4 (release_9.5.4-702-g5a49cc @ /home/jack/dev/org-mode/lisp/)
next reply other threads:[~2022-08-02 13:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 1:45 Jack Kamm [this message]
2022-08-04 2:24 ` Bug? org-id-find not finding some IDs Ihor Radchenko
2022-08-05 5:32 ` Jack Kamm
2022-08-05 12:46 ` Ihor Radchenko
2022-08-14 17:35 ` Jack Kamm
2022-08-16 4:26 ` Ihor Radchenko
2022-08-20 15:27 ` Jack Kamm
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://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r11zifjy.fsf@gmail.com \
--to=jackkamm@tatersworld.org \
--cc=emacs-orgmode@gnu.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).