From 2c9f259d65bff762f026bad98aeabafbf86e7285 Mon Sep 17 00:00:00 2001 From: Cheong Yiu Fung Date: Mon, 13 May 2019 23:37:43 +0800 Subject: [PATCH] org-manual: Small fixes * doc/org-manual.org (Handling Links): Update variable `org-id-link-to-org-use-id', which was changed in v7.9.2. TINYCHANGE --- doc/org-manual.org | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/org-manual.org b/doc/org-manual.org index 15483490b..962b432e7 100644 --- a/doc/org-manual.org +++ b/doc/org-manual.org @@ -3252,12 +3252,12 @@ current buffer: points to the target. Otherwise it points to the current headline, which is also the description[fn:30]. - #+vindex: org-link-to-org-use-id + #+vindex: org-id-link-to-org-use-id #+cindex: @samp{CUSTOM_ID}, property #+cindex: @samp{ID}, property If the headline has a =CUSTOM_ID= property, store a link to this custom ID. In addition or alternatively, depending on the value - of ~org-link-to-org-use-id~, create and/or use a globally unique + of ~org-id-link-to-org-use-id~, create and/or use a globally unique =ID= property for the link[fn:31]. So using this command in Org buffers potentially creates two links: a human-readable link from the custom ID, and one that is globally unique and works even if