From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastian Rose Subject: Re: Custom_ID problem with org-info.js display Date: Tue, 21 Apr 2009 16:16:42 +0200 Message-ID: <87fxg22it1.fsf@kassiopeya.MSHEIMNETZ> References: <878wlu4504.fsf@kassiopeya.MSHEIMNETZ> <1C0AD4AD-93F3-4E5E-B8CB-FA977F0523C9@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LwGiv-0001yx-1C for emacs-orgmode@gnu.org; Tue, 21 Apr 2009 10:13:21 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LwGip-0001xa-UD for emacs-orgmode@gnu.org; Tue, 21 Apr 2009 10:13:20 -0400 Received: from [199.232.76.173] (port=40770 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LwGip-0001xR-SL for emacs-orgmode@gnu.org; Tue, 21 Apr 2009 10:13:15 -0400 Received: from mail.gmx.net ([213.165.64.20]:56409) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1LwGip-0005Ze-2k for emacs-orgmode@gnu.org; Tue, 21 Apr 2009 10:13:15 -0400 In-Reply-To: <1C0AD4AD-93F3-4E5E-B8CB-FA977F0523C9@gmail.com> (Carsten Dominik's message of "Tue, 21 Apr 2009 14:19:17 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Carsten Dominik Cc: emacs-orgmode@gnu.org, Xin Shi Hmm - the script supports two kinds of human readable IDs now. The old ones (which where defined in the anchor inside the the headline), and the new ones, which are now defined in the headlines 'id' property. Which one is now to prefer? What I did now, is to remove the regexp search at all (`^sec-') and switched to prefer the ID in the anchor (to be backward compatible). Is there a need for numeric `sec-x.x' IDs? To put that in again is not a big deal. Sebastian Carsten Dominik writes: > On Apr 21, 2009, at 1:31 PM, Sebastian Rose wrote: > >> >> >> OK. Should work now. >> >> Old human readable IDs in headline's anchors are still prefered. >> >> Also, org-info.js is now minified (no obfuscation) to decrease the file >> size by about 40%. >> >> For those interested in hacking it, the plain org-info.js was moved to >> org-info-src.js. >> >> >> You may pull the script from the usual sources. E.g: >> >> http://repo.or.cz/w/Worg.git?a=blob_plain;f=code/org-info-js/org-info.js;hb=31f6317f2aaebe18ea8ec3a9e0a5b0426e062164 > > Hi Sebastian, > > this looks great. However: > > Let's look at the first heading now in Changes.html: > >
>

Version 6.26

>
> > As you can see, in this case, where there is a custom ID "v6.26" that is used, > I have added "sec-1" as an anchor to the headline, just to make sure that the > full systemacs of sec-NN anchors remains available. > > However, it seems that the link extraction commands "l" and "L" now both access > the sec-1 name. I believe it would be better, in this case, to use v6.26. > > - Carsten >