From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Jacob Gerlach <jacobgerlach@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [RFC][PATCH] Store links to named elements
Date: Thu, 26 Mar 2015 21:34:15 +0100 [thread overview]
Message-ID: <87h9t7lcqg.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAA6UvuEDLKqNmL4FAx1BL_uuxHnkRhPi9BMSF1kXR+jJkrQr3A@mail.gmail.com> (Jacob Gerlach's message of "Wed, 18 Mar 2015 10:19:31 -0400")
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
prev parent reply other threads:[~2015-03-26 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 14:19 [RFC][PATCH] Store links to named elements Jacob Gerlach
2015-03-26 20:34 ` Nicolas Goaziou [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h9t7lcqg.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=jacobgerlach@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).