From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Custom_ID problem with org-info.js display Date: Tue, 21 Apr 2009 16:36:17 +0200 Message-ID: <4314B5E0-2FEC-4A7C-B128-10481BB3CB39@gmail.com> References: <878wlu4504.fsf@kassiopeya.MSHEIMNETZ> <1C0AD4AD-93F3-4E5E-B8CB-FA977F0523C9@gmail.com> <87fxg22it1.fsf@kassiopeya.MSHEIMNETZ> Mime-Version: 1.0 (Apple Message framework v930.3) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LwH5H-0001vY-01 for emacs-orgmode@gnu.org; Tue, 21 Apr 2009 10:36:27 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LwH5B-0001vI-Fg for emacs-orgmode@gnu.org; Tue, 21 Apr 2009 10:36:25 -0400 Received: from [199.232.76.173] (port=58746 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LwH5B-0001vF-79 for emacs-orgmode@gnu.org; Tue, 21 Apr 2009 10:36:21 -0400 Received: from mail-fx0-f166.google.com ([209.85.220.166]:44570) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LwH5A-0002l4-Nl for emacs-orgmode@gnu.org; Tue, 21 Apr 2009 10:36:21 -0400 Received: by fxm10 with SMTP id 10so2720668fxm.42 for ; Tue, 21 Apr 2009 07:36:19 -0700 (PDT) In-Reply-To: <87fxg22it1.fsf@kassiopeya.MSHEIMNETZ> 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: Sebastian Rose Cc: emacs-orgmode@gnu.org, Xin Shi On Apr 21, 2009, at 4:16 PM, Sebastian Rose wrote: > > > 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? Yes, for all the headings that do not have a human readable ID. > > > To put that in again is not a big deal. Please do. The algorithm could be: Look at both the ID of the

tag, and the anchors in the headline. Take the first on in the combined list that does not match sec-x.x. If none does, use the sec-... one. - Carsten > > > > > 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 >>