From: Xin <shixin111@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Custom_ID problem with org-info.js display
Date: Tue, 21 Apr 2009 19:55:51 -0400 [thread overview]
Message-ID: <49EE5D07.8080303@gmail.com> (raw)
In-Reply-To: <4314B5E0-2FEC-4A7C-B128-10481BB3CB39@gmail.com>
Hi Carsten and Sebastian,
Thanks for your quick response!
The current solution is good for me. :)
Xin
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
>
>
>>
>>
>>
>>
>> Sebastian
>>
>>
>> Carsten Dominik <carsten.dominik@gmail.com> 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:
>>>
>>> <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
>>>
>
next prev parent reply other threads:[~2009-04-21 23:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 23:54 Custom_ID problem with org-info.js display Xin Shi
2009-04-21 9:40 ` Carsten Dominik
2009-04-21 10:04 ` Sebastian Rose
2009-04-21 11:31 ` Sebastian Rose
2009-04-21 12:19 ` Carsten Dominik
2009-04-21 14:16 ` Sebastian Rose
2009-04-21 14:36 ` Carsten Dominik
2009-04-21 23:55 ` Xin [this message]
2009-04-22 0:05 ` A Mark-up rule question Xin
2009-04-22 12:21 ` Carsten Dominik
2009-04-22 14:21 ` Xin Shi
2009-04-23 7:19 ` Carsten Dominik
2009-05-06 10:30 ` Carsten Dominik
2009-05-06 13:08 ` Xin Shi
2009-05-06 13:30 ` Carsten Dominik
2009-05-06 15:35 ` Sebastian Rose
2009-05-06 15:37 ` Sebastian Rose
2009-05-06 15:41 ` Xin Shi
2009-05-07 6:42 ` Carsten Dominik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49EE5D07.8080303@gmail.com \
--to=shixin111@gmail.com \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).