Max Nikulin <maniku...@gmail.com> writes: > I am not excited by the idea of extending id links for heading > hierarchy. From my point of view it is more natural to add the ID > property to the heading that should be link target. > > Sometimes I do not mind to disambiguate heading search link by > specifying title of its ancestor. I usually add the CUSTOM_ID property > or rename heading to be unique. > > I am afraid that allowing arbitrary link types to specify path to an > element is overkill. It is not XPath and not CSS selectors.
I am looking at it from an opposite direction: we already have file: links with ::search term, but file is not a very reliable link anchor. File ID will persist even when the file is moved. So, instead of having something like <file:/path/to/foo.org::* Heading>, we should better also provide <id:ID::*heading> with ID defined in the top-level property drawer. ID being some sub-heading is then a natural extension of the same idea. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
