[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Internal link to resulting image from source block
From: |
Ihor Radchenko |
Subject: |
Re: Internal link to resulting image from source block |
Date: |
Thu, 04 Aug 2022 10:37:53 +0800 |
reza <reza@housseini.me> writes:
> Hi List
>
> I'm exporting a plantuml figure to HTML like
>
> #+name: html transformation
> #+begin_src plantuml :file img/transformation-html.svg :exports results
> file org
> file html
> org -> html : org-html-publish-to-html
> #+end_src
>
> Now I want to include an internal link to this figure with ~[[html
> transformation]]~ but when I export I always get "Unable to resolve
> link". Any idea what I'm doing wrong?
Nothing really wrong on your side. It is probably an omission on the Org
side.
Executing the above code produces
#+RESULTS: html transformation
[[file:img/transformation-html.svg]]
However, it is currently impossible to link to such results paragraph by
itself - only to the parent src block. Since you are using :exports
results, the export code does not "see" the src block; only the results
block which cannot be referenced. Hence, the error.
They way to work around the problem is providing explicit name anchor to
the results block:
------------
#+name: html transformation
#+begin_src plantuml :file img/transformation-html.svg :exports results :mkdirp
yes
file org
file html
org -> html : org-html-publish-to-html
#+end_src
#+name: html transformation result
#+RESULTS: html transformation
[[file:img/transformation-html.svg]]
Now I want to include an internal link to this figure with [[html
transformation result]]. This works now.
------------
Though I do agree that the current behaviour is not intuitive in this
specific scenario. When a user provides :exports results, it would make
sense to inherit all the affiliated keywords, including #+name and
possibly various #+attr_* to the results of evaluation.
On the other hand, inheriting may be tricky. I can imagine situations
when such inheritance is not desired and a user actually prefers to
state the results keywords manually.
I am not sure what would be the best way to handle the situation at hand
while not breaking the other :exports variants.
Best,
Ihor
- Internal link to resulting image from source block, reza, 2022/08/03
- Re: Internal link to resulting image from source block,
Ihor Radchenko <=
- Message not available
- Re: Internal link to resulting image from source block, reza, 2022/08/04
- Re: Internal link to resulting image from source block, Ihor Radchenko, 2022/08/04
- Message not available
- Re: Internal link to resulting image from source block, reza, 2022/08/05
- [PATCH] org-export: Make results of named code blocks a valid link, Ihor Radchenko, 2022/08/05
- Message not available
- Re: [PATCH] org-export: Make results of named code blocks a valid link, reza, 2022/08/08
- Re: [PATCH] org-export: Make results of named code blocks a valid link, Ihor Radchenko, 2022/08/08
- Re: [PATCH] org-export: Make results of named code blocks a valid link, Ihor Radchenko, 2022/08/22