emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: doltes <doltes512@gmail.com>
To: Samuel Wales <samologist@gmail.com>
Cc: arozbiz@gmail.com, emacs-orgmode@gnu.org
Subject: Re: How can I keep Org-id links from breaking when moving files?
Date: Wed, 20 Jan 2021 06:39:16 -0500	[thread overview]
Message-ID: <87lfcn3kij.fsf@gmail.com> (raw)
In-Reply-To: <CAJcAo8soVOniCUegvw6+rkYdB5CkPe3Rd8hEXwu7b8YbVOA1fA@mail.gmail.com>

Yeah, I also found that confusing. Basically, because both mean the

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 form (FILE ID).

+ =org-id-files=: List of files which contain ID definitions.

  reply	other threads:[~2021-01-20 11:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-19  2:52 arozbiz
2021-01-19 18:32 ` doltes
2021-01-20  0:13   ` Samuel Wales
2021-01-20 11:39     ` doltes [this message]
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:

  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=87lfcn3kij.fsf@gmail.com \
    --to=doltes512@gmail.com \
    --cc=arozbiz@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=samologist@gmail.com \
    --subject='Re: How can I keep Org-id links from breaking when moving files?' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:


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).