[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Orgmode] Custom_ID problem with org-info.js display

From: Xin
Subject: Re: [Orgmode] Custom_ID problem with org-info.js display
Date: Tue, 21 Apr 2009 19:55:51 -0400
User-agent: Mozilla-Thunderbird (X11/20090103)

Hi Carsten and Sebastian,

Thanks for your quick response!

The current solution is good for me.  :)


Carsten Dominik wrote:

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 <h3> 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


Carsten Dominik <address@hidden> 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

You may pull the script from the usual sources. E.g:


Hi Sebastian,

this looks great.  However:

Let's look at the first heading now in Changes.html:

<div id="outline-container-v6.26" class="outline-2">
<h2 id="v6.26"><a name="sec-1" id="sec-1"></a>Version 6.26 </h2>
<div class="outline-text-2" id="text-v6.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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]