From: Daimrod <daimrod@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Link to named block
Date: Mon, 20 Oct 2014 19:51:19 +0200 [thread overview]
Message-ID: <87siiiociw.fsf@tanger.home> (raw)
In-Reply-To: <878ukbaxs2.fsf@bzg.ath.cx> (Bastien's message of "Mon, 20 Oct 2014 11:35:57 +0200")
[-- Attachment #1: Type: text/plain, Size: 1323 bytes --]
Bastien <bzg@gnu.org> writes:
> Hi Greg,
Hi Bastien,
> Daimrod <daimrod@gmail.com> writes:
>
>> I've made a small function to link to a named block in org files.
>>
>> #+BEGIN_SRC emacs-lisp
>> (defun dmd--org-link-to-named-block ()
>> "Create an org-link to the named block at point.
>>
>> Blocks are named with #+NAME."
>> (when (eq major-mode 'org-mode)
>> (let* ((el (org-element-at-point))
>> (name (org-element-property :name el)))
>> (when name
>> (org-store-link-props
>> :link name)))))
>> #+END_SRC
>>
>> Do you think it should be added to org? I find it useful to add a link
>> to a figure when I'm exporting to latex.
>
> I'm not sure how to use the function above -- how do you set the link
> itself, not just its properties?
I don't. The link name is enough because named block usually have "nice"
name. For example, given the following named block:
#+NAME: fig:my-fig
[[file:my-fig.png]]
Then link will be [[fig:my-fig]].
>> I tried to add it to `org-store-link` but it's a big function and I
>> wonder why it's not splitted in smaller functions. (e.g.
>> org-help-store-link, org-w3-store-link, org-image-store-link, ...).
>> If you agree, I could split it.
>
> Yes, please go ahead.
noted.
--
Daimrod/Greg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
prev parent reply other threads:[~2014-10-20 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 12:43 Link to named block Daimrod
2014-10-20 9:35 ` Bastien
2014-10-20 17:51 ` Daimrod [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=87siiiociw.fsf@tanger.home \
--to=daimrod@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
/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).