From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Daniel Clemente <n142857@gmail.com>
Cc: tftorrey@tftorrey.com, emacs-orgmode@gnu.org, Rasmus <rasmus@gmx.us>
Subject: Re: Bug: HTML export ignoring CUSTOM_ID properties
Date: Thu, 23 Apr 2015 21:21:29 +0200 [thread overview]
Message-ID: <87pp6u1why.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87h9s63e4p.wl-n142857@gmail.com> (Daniel Clemente's message of "Fri, 24 Apr 2015 01:15:18 +0700")
Daniel Clemente <n142857@gmail.com> writes:
> While the two systems work, I don't see either why the #orgheadline129
> system is better than the #sec-1-4-3-1-2.
Actually is is better because it is consistent. "sec-1-4-3-1-2" is
almost as fragile and doesn't play nice with unnumbered headlines.
However, this is not the reason why this change was introduced.
I explained it already.
> Not important enough to justify a breaking change either.
This is not really a breaking change. AFAIK, "sec-x.x.x" labelling was
never made public. However, you can use CUSTOM_ID to enforce some label
and then refer to it.
> IDs are not only internal. CSS knows about it, JS too, and URLs can be
> built and shared through the web that include org IDs
> (myweb.com/somedoc.html#someid).
ID not specified by the user are internal. "sec-x-x" is an internal
scheme. You can still use CUSTOM_ID for that.
Of course, it is also possible to add an anchor with id "sec-x-x" to
numbered headlines only (maybe as an opt-in so newcomers can at least
read about it). However, I suspect that a filter can do as well.
Regards,
prev parent reply other threads:[~2015-04-23 19:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 23:19 Bug: HTML export ignoring CUSTOM_ID properties T.F. Torrey
2015-04-17 0:20 ` Rasmus
2015-04-17 18:20 ` T.F. Torrey
2015-04-18 13:57 ` Rasmus
2015-04-18 18:26 ` T.F. Torrey
2015-04-18 22:38 ` Aaron Ecay
2015-04-19 3:40 ` T.F. Torrey
2015-04-18 23:08 ` Nicolas Goaziou
2015-04-19 4:20 ` T.F. Torrey
2015-04-19 9:08 ` Nicolas Goaziou
2015-04-19 21:11 ` T.F. Torrey
2015-04-19 14:47 ` Rasmus
2015-04-21 5:37 ` Daniel Clemente
2015-04-21 7:25 ` Nicolas Goaziou
2015-04-23 18:15 ` Daniel Clemente
2015-04-23 19:21 ` Nicolas Goaziou [this message]
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=87pp6u1why.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=n142857@gmail.com \
--cc=rasmus@gmx.us \
--cc=tftorrey@tftorrey.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).