Le vendredi 8 mars 2013 à 23h35, Bastien a écrit:
> Can you update your patch mentioning this and adding a commit message
> and adding TINYCHANGE at the end?
Here it is.
François
>From 169d8382f01b8914e002313032c2d123c86b913a Mon Sep 17 00:00:00 2001
From: François Allisson <franc...@allisson.co>
Date: Wed, 9 Jan 2013 12:32:09 +0100
Subject: [PATCH] org.texi: Update documentation on internal link handling
* Update 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'.
* Mention the need to load the org-id library.
TINYCHANGE
---
doc/org.texi | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 8b0a59f..c6e5b70 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -3445,13 +3445,16 @@ 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{The library @code{org-id}
+must first be loaded, either through @code{org-customize} by enabling
+@code{id} in @code{org-modules} , or by adding @code{(require 'org-id)} 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
