On 25.01.2024 13:41, Ihor Radchenko wrote:
gerard.vermeu...@posteo.net writes:
I have found that CAPTION keywords in the "name-result-example" in
the
manual are essential to produce correct links.
It should not be essential. What you demonstrated is two bugs in Org
mode.
In case the
gerard.vermeu...@posteo.net writes:
> I have found that CAPTION keywords in the "name-result-example" in the
> manual are essential to produce correct links.
It should not be essential. What you demonstrated is two bugs in Org mode.
> In case the relevant blocks have e.g. ":exports both", Org
On 22.01.2024 19:59, Ihor Radchenko wrote:
gerard.vermeu...@posteo.net writes:
FR: would it be possible to resolve such links?
What is the purpose? Why not simply leaving the result name same as
the
source block?
I have Python "IN" blocks generating Python "OUT" blocks that may end
up
gerard.vermeu...@posteo.net writes:
>>> FR: would it be possible to resolve such links?
>>
>> What is the purpose? Why not simply leaving the result name same as the
>> source block?
>
> I have Python "IN" blocks generating Python "OUT" blocks that may end up
> on different pages after exporting
On 22.01.2024 19:15, Ihor Radchenko wrote:
gerard.vermeu...@posteo.net writes:
For the listings below org-lint tells me to move "#+name: OUT"
downwards:
Line Trust Warning
17 high #+name: in results of evaluation will be replaced by
re-evaluating the src block. Use
gerard.vermeu...@posteo.net writes:
> For the listings below org-lint tells me to move "#+name: OUT"
> downwards:
>
> Line Trust Warning
> 17 high #+name: in results of evaluation will be replaced by
> re-evaluating the src block. Use #+name in the block instead.
>
> This is
For the listings below org-lint tells me to move "#+name: OUT"
downwards:
Line Trust Warning
17 high #+name: in results of evaluation will be replaced by
re-evaluating the src block. Use #+name in the block instead.
This is not true, and after I move it below "#+RESULTS: IN"
