From: "François Allisson" <francois@allisson.co>
To: Bastien <bzg@altern.org>
Cc: Org mode <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] Update documentation on handling internal links
Date: Wed, 09 Jan 2013 12:42:16 +0100 [thread overview]
Message-ID: <8738ya37mv.fsf@allisson.co> (raw)
In-Reply-To: <87ip772tgy.fsf@bzg.ath.cx>
[-- Attachment #1: Type: text/plain, Size: 194 bytes --]
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
[-- Attachment #2: 0001-org.texi-Update-documentation-on-internal-link-handl.patch --]
[-- Type: text/x-diff, Size: 1896 bytes --]
From 169d8382f01b8914e002313032c2d123c86b913a Mon Sep 17 00:00:00 2001
From: François Allisson <francois@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
next prev parent reply other threads:[~2013-01-09 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 21:10 [PATCH] Update documentation on handling internal links François Allisson
2013-01-08 22:35 ` Bastien
2013-01-09 11:42 ` François Allisson [this message]
2013-01-09 11:53 ` Bastien
2013-01-09 12:50 ` François Allisson
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=8738ya37mv.fsf@allisson.co \
--to=francois@allisson.co \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).