org-store-link relative to parent headings

org-store-link relative to parent headings

[a4ofubmq]

I'd like to propose an alternative method to format links (org-store-
link) that would include parents of a heading. For example in a
document like this:

* heading 1
** subheading 1
* heading 2
** subheading 1

there is ambiguity right now if you want to org-store-link to heading 2
> subheading 1. By default org stores
[[file:<FILENAME>::*subheading1]], which would incorrectly point to
heading 1.

Instead it could be [[file:<FILENAME>::*heading 2**subheading1]]

Please let me know what you think, if this has been already suggested.
I know that you could create unique UUID in PROPERTIES, but wouldn't it
be more informative if org-store-link used parent headings instead? I
think it would be more elegant and not dissimilar from other popular
addressing schemes (e.g. file paths or urls).

reference stackoverflow question:
https://emacs.stackexchange.com/questions/82234/org-store-link-relative-to-parent?noredirect=1#comment138536_82234

[FR] Allow searching by outline path in file: links to Org files [file:<filename::*parent heading::*child] (was: org-store-link relative to parent headings)

[Ihor Radchenko]

a4ofubmq@anonaddy.com writes:

> there is ambiguity right now if you want to org-store-link to heading 2
>> subheading 1. By default org stores
> [[file:<FILENAME>::*subheading1]], which would incorrectly point to
> heading 1.
>
> Instead it could be [[file:<FILENAME>::*heading 2**subheading1]]
>
> Please let me know what you think, if this has been already suggested.
> I know that you could create unique UUID in PROPERTIES, but wouldn't it
> be more informative if org-store-link used parent headings instead? I
> think it would be more elegant and not dissimilar from other popular
> addressing schemes (e.g. file paths or urls).

I think that such feature does make sense.
In a way, we already use something similar in org-refile - search by
outline path.

I am not sure if I like the format you proposed though.
Maybe we can instead try to implement nested search options. Something
like [file:<filename>::*heading 2::*subheading1]

You may refer to the existing code in `org-id-open' that allows to
narrow down link search to an existing subtree.

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