From: ST <smntov@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Eric S Fraga <esflists@gmail.com>,
org-mode-email <Emacs-orgmode@gnu.org>,
Christian Moe <mail@christianmoe.com>,
John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: Structured links to headings with endless depth
Date: Wed, 14 Mar 2018 20:46:55 +0200 [thread overview]
Message-ID: <1521053215.1930.124.camel@gmail.com> (raw)
In-Reply-To: <873712ld8z.fsf@nicolasgoaziou.fr>
On Wed, 2018-03-14 at 19:32 +0100, Nicolas Goaziou wrote:
> ST <smntov@gmail.com> writes:
>
> > Why [[file.org::#1:2:1]] is nicer than [file.org::1:2:1]]?
>
> Because you can write something more meaningful than "1:2:1" when using
> a CUSTOM_ID.
>
> >> - it translates nicely to "id" tag in HTML.
> >
> > You can generate the "id" tag in HTML like this 1-2-1 (if HTML dislikes
> > 1:2:1 tag)
>
> CUSTOM_ID is built-in, without implementing anything.
>
> > Isn't a good idea to add such a built in link type in the long term?
>
> IMO, Org has enough internal link types.
>
> In particular, this one brings little value compared to CUSTOM_ID. It is
> fragile wrt re-ordering, refiling, capture... It may be a headache to
> export, too, because "1.2.1" may mean something entirely different once
> non-exportable trees have been pruned.
Sure, numbers were just a short abstract example. This can very well be:
fruits:apples:jonagold
>
> No offence intended, but it really sounds like a false good idea.
You definitely have more experience with org (I'm just learning), so you
indeed know better :)
next prev parent reply other threads:[~2018-03-14 18:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 10:09 Structured links to headings with endless depth ST
2018-03-12 10:29 ` Eric S Fraga
2018-03-12 10:39 ` ST
2018-03-12 13:08 ` Christian Moe
2018-03-12 13:46 ` ST
2018-03-12 14:10 ` Nicolas Goaziou
2018-03-12 15:08 ` ST
2018-03-14 3:49 ` John Kitchin
2018-03-14 6:58 ` Michael Brand
2019-05-06 16:34 ` Michael Brand
2019-05-07 3:26 ` Ihor Radchenko
2019-05-07 14:39 ` Michael Brand
2019-05-18 10:44 ` Ihor Radchenko
2018-03-14 10:10 ` ST
2018-03-14 13:26 ` Nicolas Goaziou
2018-03-14 18:11 ` ST
2018-03-14 18:32 ` Nicolas Goaziou
2018-03-14 18:46 ` ST [this message]
2018-03-14 14:15 ` John Kitchin
2018-03-14 18:07 ` ST
2018-03-12 12:43 ` ST
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=1521053215.1930.124.camel@gmail.com \
--to=smntov@gmail.com \
--cc=Emacs-orgmode@gnu.org \
--cc=esflists@gmail.com \
--cc=jkitchin@andrew.cmu.edu \
--cc=mail@christianmoe.com \
--cc=mail@nicolasgoaziou.fr \
/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).