Re: Bug: HTML export ignoring CUSTOM_ID properties

[Nicolas Goaziou <mail@nicolasgoaziou.fr>]

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.

> With a flat numbering like #orgheadline129, deleting any headline
> would change the IDs of all headers after it.

True. This was already the case before, as explained above, or when
using unnumbered headlines.

> 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).

I'm not against re-using CUSTOM_ID as in "outline-container-CUSTOM_ID",
but in the general case, where no CUSTOM_ID is defined, the current
state is fine by me.


Regards,

-- 
Nicolas Goaziou