> > 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.
Yes, exactly and formatting you proposed makes sense to me as well.
