From: Diego Zamboni <diego@zzamboni.org>
To: Budiman Snowman <budimansnowman@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Disambiguate internal links?
Date: Fri, 5 Jun 2020 13:01:09 +0200 [thread overview]
Message-ID: <CAGY83EcJDSBpNL-R+W+qYReJKTZG7b-4SOsAzA8pORyT6=dM_w@mail.gmail.com> (raw)
In-Reply-To: <CA+YqxJ6mxLSrUYdYNFWDVYjwj+t=UgAE3ZCnbuW0VN9mWrLPHw@mail.gmail.com>
I personally find CUSTOM_ID's easier since I can make them
unequivocally unique, and by using them the links don't break if I
change something in the headline title.
On Thu, Jun 4, 2020 at 5:26 PM Budiman Snowman <budimansnowman@gmail.com> wrote:
>
> On Wed, Jun 3, 2020 at 9:21 PM Diego Zamboni <diego@zzamboni.org> wrote:
>>
>> I almost always use a CUSTOM_ID property for this, e.g.
>>
>> * topic1
>> See topic [[#topic2][topic2]].
>> See glossary [[#glossary_topic2][topic2]].
>>
>> * topic2
>> :PROPERTIES:
>> :CUSTOM_ID: topic2
>> :END:
>>
>> * glossary
>> ** topic1
>> :PROPERTIES:
>> :CUSTOM_ID: glossary_topic2
>> :END:
>> ** topic2
>> :PROPERTIES:
>> :CUSTOM_ID: glossary_topic2
>> :END:
>>
>
> Are there advantages to using CUSTOM_ID instead of dedicated target? I'll stick with dedicated target for now, because it's shorter to type.
>
> Regards,
> BS
>
next prev parent reply other threads:[~2020-06-05 11:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 14:06 Disambiguate internal links? Budiman Snowman
2020-06-03 14:17 ` Eric S Fraga
2020-06-03 14:20 ` Diego Zamboni
2020-06-04 15:26 ` Budiman Snowman
2020-06-05 11:01 ` Diego Zamboni [this message]
2020-09-04 14:47 ` Bastien
2020-10-09 1:13 ` Budiman Snowman
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='CAGY83EcJDSBpNL-R+W+qYReJKTZG7b-4SOsAzA8pORyT6=dM_w@mail.gmail.com' \
--to=diego@zzamboni.org \
--cc=budimansnowman@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).