On 2021-01-21 08:14, aroz...@gmail.com wrote:
there's no way to programmatically make sure that Org can find those
IDs again (since there's no way to simply add a folder, rather than a
list of files, to =org-id-locations= or =org-id-files=?
Being that this is Emacs, you can do almost anything
This is helpful clarification, thank you. But does that mean that, if I
change the directory where some files with UUIDs are located, there's no
way to programmatically make sure that Org can find those IDs again (since
there's no way to simply add a folder, rather than a list of files, to
Yeah, I also found that confusing. Basically, because both mean the
same.
I think that a better description for those variables would be
+ =org-id-locations=: List obtained from `org-id-locations-file'. This
list maps each ID to the file in which the definition occurs. It
contains lists of the
(defvar org-id-locations nil
"List of files with IDs in those files.")
(defvar org-id-files nil
"List of files that contain IDs.")
you are in a maze of twisty little passages.
you are in a twisty maze of little passages.
On 1/19/21, doltes wrote:
>
> aroz...@gmail.com writes:
>
>> This
aroz...@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
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
