Re: [RFC][PATCH] Store links to named elements

[Nicolas Goaziou <mail@nicolasgoaziou.fr>]

Hello,

Jacob Gerlach <jacobgerlach@gmail.com> writes:

> In [1], storing links to named elements was discussed. AFAICT, no
> patches came from that discussion. The current behavior is that given:
>
> * Headline
>
> #+Name: foo
>
> org-store-link will store a link to `*Headline' rather than `foo'.
>
> Attached is a very rough first attempt at patching org-store-link to
> recognize and link to the name.
>
> Is this approach worth fleshing out or are there problems associated
> with this type of link? Using the above example, [[foo]] seems to be a
> valid link, recognized by both export and org-open-at-point.
>
> If doable, a couple of specific questions:
> This attached patch makes no attempt to store the file name as
> currently done for headlines. Would it be better to check for a name
> in the headline linking code (the final "t" in the org-mode-p `cond'
> in org-store-link) or rather reproduce file name code separately.

The problem is that links to #+NAME are internal, i.e., they doesn't
behave well when targeting a different document. Therefore, I'm not sure
there's a real benefit from automating it. Links to headlines are much
more robust.

> Does a context string make sense for links to element names?

No, it doesn't.


Regards,

-- 
Nicolas Goaziou