From: Ihor Radchenko <firstname.lastname@example.org>
To: reza <email@example.com>
Cc: "firstname.lastname@example.org" <email@example.com>
Subject: Re: Internal link to resulting image from source block
Date: Fri, 05 Aug 2022 09:48:37 +0800 [thread overview]
Message-ID: <87bkszpiiy.fsf@localhost> (raw)
reza <firstname.lastname@example.org> writes:
>> 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
>> #+name: html transformation result
>> #+RESULTS: html transformation
>> 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.
> Shall I file a bug report? As a beginner I assumed that the name tag
> gets carried over to the result and I still think it is a sensible
> solution, but I could imagine that is perhaps not a very explicit behavior.
This email is already a bug report :)
However, we cannot just blindly carry over the name tag to the result.
Consider a case when you have ":results both" in your src block. Where
should the [[html transformation]] link refer to? The src block? The
next prev parent reply other threads:[~2022-08-05 1:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <email@example.com>
2022-08-03 21:13 ` reza
2022-08-04 2:37 ` Ihor Radchenko
[not found] ` <firstname.lastname@example.org>
2022-08-04 17:21 ` reza
2022-08-05 1:48 ` Ihor Radchenko [this message]
[not found] ` <email@example.com>
2022-08-05 6:34 ` reza
2022-08-05 10:15 ` [PATCH] org-export: Make results of named code blocks a valid link Ihor Radchenko
[not found] ` <firstname.lastname@example.org>
2022-08-08 10:59 ` reza
2022-08-08 12:21 ` Ihor Radchenko
2022-08-22 12:01 ` Ihor Radchenko
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).