From: Cheong Yiufung <cheongyiufung@gmail.com>
To: emacs-orgmode list <emacs-orgmode@gnu.org>
Subject: [PATCH] Manual update
Date: Thu, 16 May 2019 11:26:58 +0800 [thread overview]
Message-ID: <87v9ybw03h.fsf@gmail.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: org-manual-fixes --]
[-- Type: text/x-patch, Size: 1825 bytes --]
From 14ff6eb2b451471514206d5126c0af02125ec7e6 Mon Sep 17 00:00:00 2001
From: Cheong Yiu Fung <cheongyiufung@gmail.com>
Date: Mon, 13 May 2019 22:51:08 +0800
Subject: [PATCH] org-manual: Small fixes
* doc/org-manual.org (Handling Links): update variable
`org-id-link-to-org-use-id', which is changed in v7.9.2.
---
doc/org-manual.org | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index 54b89e5bf..c519d310b 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -3173,17 +3173,17 @@ current buffer:
to the target. Otherwise it points to the current headline, which
is also the description[fn:28].
- #+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 =ID=
- property for the link[fn:29]. 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 the entry is
- moved from file to file. Later, when inserting the link, you need
- to decide which one to use.
+ ~org-id-link-to-org-use-id~, create and/or use a globally unique
+ =ID= property for the link[fn:29]. 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 the
+ entry is moved from file to file. Later, when inserting the link,
+ you need to decide which one to use.
- /Email/News clients: VM, Rmail, Wanderlust, MH-E, Gnus/ ::
--
2.21.0
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
Hi there, here's a small patch the fixes mentions of
`org-link-to-org-use-id' to `org-id-link-to-org-use-id' in the manual.
Hope it helps.
---
Cheong Yiufung
next reply other threads:[~2019-05-16 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 3:26 Cheong Yiufung [this message]
2019-06-07 21:34 ` [PATCH] Manual update Nicolas Goaziou
2019-06-07 22:25 ` Kyle Meyer
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=87v9ybw03h.fsf@gmail.com \
--to=cheongyiufung@gmail.com \
--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).