From: Daniel Clemente <n142857@gmail.com>
To: Rasmus <rasmus@gmx.us>,
tftorrey@tftorrey.com, emacs-orgmode@gnu.org,
Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Bug: HTML export ignoring CUSTOM_ID properties
Date: Fri, 24 Apr 2015 01:15:18 +0700 [thread overview]
Message-ID: <87h9s63e4p.wl-n142857@gmail.com> (raw)
In-Reply-To: <877ft6aqp2.fsf@nicolasgoaziou.fr>
El Tue, 21 Apr 2015 09:25:13 +0200 Nicolas Goaziou va escriure:
>
> Hello,
>
> Daniel Clemente <n142857@gmail.com> writes:
>
> > I also saw this change (diff format):
> >
> > -<div id="outline-container-sec-1-4-3-1-2" class="outline-6">
> > -<h6 id="sec-1-4-3-1-2"><span class="section-number-6">1.4.3.1.2</span> tercer error con stash</h6>
> > +<div id="outline-container-orgheadline129" class="outline-6">
> > +<h6 id="orgheadline129"><span class="section-number-6">1.4.3.1.2</span> tercer error con stash</h6>
> >
> > The #sec-1-4-3-1-2 format was better. If I delete section 1.4.3.1.2,
> > section 1.5 is still called 1.5, that's good.
>
> And if you delete section 1.4, section 1.5 is no longer called 1.5. So
> you need to update IDs most times you change headline numbering. I don't
> think it is really better than the current state.
>
It's good to minimize the number of changes after each export. I prefer to review 10 changes rather than 200. I cannot just forget and let the automatic export work its way; I need to review it because in every export I find many different export bugs or unexpected features.
While the two systems work, I don't see either why the #orgheadline129 system is better than the #sec-1-4-3-1-2. Not important enough to justify a breaking change either.
> > And what's the use of IDs if they're not permanent?
>
> The point is that Org knows the ID associated to a given headline, and
> provides tools to access them (`org-export-get-reference' for back-end
> developers, [[*tercer error con stash]] for users).
>
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).
next prev parent reply other threads:[~2015-04-23 18:15 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 [this message]
2015-04-23 19:21 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h9s63e4p.wl-n142857@gmail.com \
--to=n142857@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.