Hi,
The attached documentation patch updates the mention to the obsolete
variable `org-link-to-org-use-id' with a mention to the newer variable
`org-id-link-to-org-use-id'.
Furthermore, it mentions that (require 'org-id) is necessary for
`org-id-link-to-org-use-id' to work. Perhaps it is not what should be
done. Shall org-id be required by default?
Best,
and thanks all for 7.9.3a ! I'm testing.
François
>From 0dc2100e3ce1da1f6a5738dd0cbc13e39d39e433 Mon Sep 17 00:00:00 2001
From: François Allisson <franc...@allisson.co>
Date: Tue, 8 Jan 2013 21:54:19 +0100
Subject: [PATCH] org.texi: Update documentation on `org-id-link-to-org-use-id'
---
doc/org.texi | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 6625ed8..35adfa9 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -3445,13 +3445,15 @@ be the description@footnote{If the headline contains a timestamp, it will be
removed from the link and result in a wrong link---you should avoid putting
timestamp in the headline.}.
-@vindex org-link-to-org-use-id
+@vindex org-id-link-to-org-use-id
@cindex property, CUSTOM_ID
@cindex property, ID
If the headline has a @code{CUSTOM_ID} property, a link to this custom ID
will be stored. In addition or alternatively (depending on the value of
-@code{org-link-to-org-use-id}), a globally unique @code{ID} property will be
-created and/or used to construct a link. So using this command in Org
+@code{org-id-link-to-org-use-id}), a globally unique @code{ID} property will
+be created and/or used to construct a link@footnote{In order to use
+@code{org-id} facilities, @code{(require 'org-id)} has to be found in your
+@file{.emacs}.}. So using this command in Org
buffers will potentially create two links: a human-readable from the custom
ID, and one that is globally unique and works even if the entry is moved from
file to file. Later, when inserting the link, you need to decide which one
--
1.7.10.4
