From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: Nathan Neff <nathan.neff@gmail.com>Nathan Neff
<nathan.neff@gmail.com>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: CUSTOM_ID vs ID
Date: Thu, 01 Aug 2019 09:55:36 +0200 [thread overview]
Message-ID: <87tvb1b9qf.fsf@aquinas.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <CAC=HedC+ChHz3PKNorY9ihmdHDZfj-sF+zQmd4sbAN4gitTbfA@mail.gmail.com>
Hi Nate,
Nathan Neff <nathan.neff@gmail.com> writes:
> However, I usually *do* manually assign IDs (not CUSTOM_IDs) myself.
> The reason is so I can reasonably search for the ID within my org
> files and that the link ID makes some sense to me.
>
> For example, if I see a link to "id:keyboard_shortcuts" I can tell where
> it's going.
If this is what you want IDs for, then you probably want CUSTOM_ID.
There is built-in Org syntax for links based on CUSTOM_ID: write your
links like [[#some-custom-id]] or [[file:foo.org::#some-custom-id]].
And if you use CUSTOM_ID, then if you ever need ID later (e.g., for
something like org-caldav), you won't have a collision between the two
different properties.
--
Best,
Richard
next prev parent reply other threads:[~2019-08-01 7:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-27 23:35 CUSTOM_ID vs ID Nathan Neff
2019-07-28 8:10 ` Nicolas Goaziou
2019-07-29 4:23 ` David Masterson
2019-07-29 6:38 ` Nicolas Goaziou
2019-08-02 4:54 ` David Masterson
2019-07-30 0:38 ` Nathan Neff
2019-08-01 7:55 ` Richard Lawrence [this message]
2019-08-09 11:13 ` Adam Porter
2019-08-02 14:53 ` Nathan Neff
2019-08-09 11:12 ` Adam Porter
2019-08-18 0:53 ` Jorge P. de Morais Neto
2019-08-18 10:40 ` Nicolas Goaziou
2019-08-18 14:24 ` Jorge P. de Morais Neto
2019-08-18 15:05 ` Nicolas Goaziou
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=87tvb1b9qf.fsf@aquinas.i-did-not-set--mail-host-address--so-tickle-me \
--to=richard.lawrence@berkeley.edu \
--cc=nathan.neff@gmail.com \
/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).