Morgan Smith <[email protected]> writes:
> Then there is no way to link to [[*foo/bar]]
This is correct.
The typical way to address non-unique heading names issue is using ID
links and setting `org-id-link-to-org-use-id' to t.
Maybe we should document it better when introducing :comments header
argument in 16.8 Extracting Source Code.
> The manual mentions that names need to be unique and says that the linter will
> help you accomplish this. However, from my testing it appears the linter does
> not warn about duplicated heading names.
> [[info:org#Internal Links]]
The manual says
Note that you must make sure custom IDs, dedicated targets, and names
are unique throughout the document. Org provides a linter to assist you
in the process, if needed. See *note Org Syntax::.
This is talking about :ID: ..., <<target>>, and #+NAME, not about
heading titles.
> Personally, I think adding the ability to link to a heading by a path would be
> a good feature. However, according to the manual, this particular bug report
> is user error. It would be nice if a maintainer chimed in here to provide
> their opinion.
Yes, it would be a good feature. We even have a feature request for it:
https://list.orgmode.org/orgmode/87v7xwz1v8.fsf@localhost/
Note, however, that even outline-path based links may still be
ambiguous:
* Parent
** Child
** Child
This second child has exactly the same name and outline path!
--
Ihor Radchenko // yantar92,
Org mode maintainer,
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>
