Hi Sebastian,

I have an idea of testing whether it works or not.

In the orgmode page:

http://orgmode.org/Changes.html#sec-2.1.1

It's talking about the custom ID. Could you try to add an example after line:

Links written like [[#my-target-name] ] can be used to target a custom ID.

For example:  [[#v6.24][Version 6.24]] should go to the section Version 6.24.

If this link can be used, that means the  problem is solved.

Thank you!

Xin






On Fri, Jun 19, 2009 at 12:08 PM, Sebastian Rose <sebastian_rose@gmx.de> wrote:

Hm - the following methods work here. As I found in
http://article.gmane.org/gmane.emacs.orgmode/13047/match=custom+id they
shouldn't. Seems the links should be prepended with the hash sign as you
proposed. But it works both ways here (org-mode from today).  I jumped
the gun and took a look in a testfile I use here (see below).



And:

 There really _was_ a bug in org-info.js that should be fixed now.
 The current code is here:
 http://repo.or.cz/w/Worg.git?a=commit;h=366e95c4c3dd9bcca7093d6aad137fc89eadf37a

 Now we see the prefered (i.e. custom) IDs in the browser's location
 bar (and therefor the history panel, if the browser has such a thing).




This is the relevant part of a file I use here for testing:

=> --->8----------------------------->8----------------------------->8---
# <<fill-table-column-with-incremental-numbers>>
* Section C

 ...some content ...

   *These links work:*

   + [[fill-table-column-with-incremental-numbers][Section C]]
   + [[subsection-four][Subsection C.2]]


*** Subsection C.2
   :PROPERTIES:
   :CUSTOM_ID: subsection-four
   :END:

   + [[#fill-table-column-with-incremental-numbers][Section C]]
   + [[#subsection-four][Subsection C.2]]

<= ---8<-----------------------------8<-----------------------------8<---






Could you send us the part of your sources that does _not_ work?




Regards



  Sebastian