From: doltes <doltes512@gmail.com>
To: arozbiz@gmail.com
Cc: emacs-orgmode@gnu.org
Subject: Re: How can I keep Org-id links from breaking when moving files?
Date: Tue, 19 Jan 2021 13:32:56 -0500 [thread overview]
Message-ID: <87ft2wvktj.fsf@gmail.com> (raw)
In-Reply-To: <CAJniy+MN110mwbd325he2DgZbgehSEzpZdfw0s+Fi_7oVASzBw@mail.gmail.com>
arozbiz@gmail.com writes:
> This question is in the context of using Org-id UUIDs for linking between
> files. If I understand correctly, Org-id knows where to look for UUIDs
> (generated by org-id-get-create) by looking at the org-id-locations
> variable. But what if I move an .org file that I've generated a UUID into
> another folder? I know I can run org-id-update-id-locations, and there's an
> org-id-extra-files variable, but is there a way to list all the folders on
> the system where Org-id should look for UUIDs?
>
> Thanks,
> Alan
After reading the docstring of the function
=org-id-update-id-locations=, I found that the files which are scanned
are defined by 6 variables.
The following was retrieved from the docstring
#+begin_quote
This will scan all agenda files, all associated archives, and all
files currently mentioned in ‘org-id-locations’.
#+end_quote
This implies that when that function is executed, the files whose
content is searched for IDs (i.e. they are scanned) are
+ The files mentioned in =org-agenda-files=.
+ The archives associated to the files in =org-agenda-files=.
+ The files mentioned in =org-id-locations=.
+ The files provided as arguments to the =org-id-update-id-locations=.
The following are not mentioned in the documentation of
=org-id-update-id-locations=, but when looking at the source code, you
can see that the value of the following variables is used
+ =org-id-extra-files=
+ =org-id-files=
As we could see, the files which are scanned are defined by 6 variables.
Now, apparently, you want to get a list of the files which are
scanned. You can do that by executing what
=org-id-update-id-locations= executes in order to get the list of
files to scan. The following was retrieved from that function with
some modifications
#+begin_src elisp :results output
(let ((files (delete-dups
(mapcar #'file-truename
(append
(org-agenda-files t org-id-search-archives)
(unless (symbolp org-id-extra-files)
org-id-extra-files)
org-id-files)))))
(dolist (file files) (princ (format "%s\n" file))))
#+end_src
#+RESULTS:
#+begin_example
/home/username/my/org/Statistics.org
/home/username/my/org/Programming languages/Elisp.org
/home/username/my/org/Programming languages/R.org
#+end_example
Hope that helps. Let me know if that answers your question.
next prev parent reply other threads:[~2021-01-19 19:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 2:52 How can I keep Org-id links from breaking when moving files? arozbiz
2021-01-19 18:32 ` doltes [this message]
2021-01-20 0:13 ` Samuel Wales
2021-01-20 11:39 ` doltes
2021-01-21 13:14 ` arozbiz
2021-01-22 19:16 ` TRS-80
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=87ft2wvktj.fsf@gmail.com \
--to=doltes512@gmail.com \
--cc=arozbiz@gmail.com \
--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).