From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Bug: HTML export ignoring CUSTOM_ID properties Date: Tue, 21 Apr 2015 09:25:13 +0200 Message-ID: <877ft6aqp2.fsf@nicolasgoaziou.fr> References: <87twwefwgz.fsf@jack.tftorrey.com> <871tjhwnd0.fsf@gmx.us> <87k2x62gam.wl-n142857@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34398) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YkSXC-0007NP-5j for emacs-orgmode@gnu.org; Tue, 21 Apr 2015 03:23:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YkSXB-0005VO-6Z for emacs-orgmode@gnu.org; Tue, 21 Apr 2015 03:23:54 -0400 Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:38247) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YkSXB-0005VI-1B for emacs-orgmode@gnu.org; Tue, 21 Apr 2015 03:23:53 -0400 In-Reply-To: <87k2x62gam.wl-n142857@gmail.com> (Daniel Clemente's message of "Tue, 21 Apr 2015 12:37:05 +0700") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Daniel Clemente Cc: tftorrey@tftorrey.com, emacs-orgmode@gnu.org, Rasmus Hello, Daniel Clemente writes: > I also saw this change (diff format): > > -
> -
1.4.3.1.2 tercer error con stash
> +
> +
1.4.3.1.2 tercer error con stash
> > 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