emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: gerard.vermeulen@posteo.net
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Emacs orgmode <emacs-orgmode@gnu.org>
Subject: Re: [BUG] org-lint tells to move #+name to wrong place in results block
Date: Mon, 22 Jan 2024 18:50:08 +0000	[thread overview]
Message-ID: <429d681f72b1b13d81f24836017929d7@posteo.net> (raw)
In-Reply-To: <875xzls08s.fsf@localhost>



On 22.01.2024 19:15, Ihor Radchenko wrote:
> gerard.vermeulen@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 not true
> 
> Good point.
> The real problem is indeed different - when the source block has
> :exports code, results will be removed and any links to OUT will become
> invalid:
> 
>> ..., but exporting says:  Unable to resolve the link "OUT".
> 
>> 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 to LaTeX and PDF.
The FR would allow to link always to the correct page.

I have 10 org-lint warnings of this type for a 150 page PDF document.
Most of those "OUT" blocks are on the same page as their corresponding
"IN" blocks, but I have worked around this limitation.

I can live without the requested feature, but it would be a way to 
eliminate
an org-lint test.

Best regards -- Gerard

next prev parent reply	other threads:[~2024-01-22 18:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 17:47 [BUG] org-lint tells to move #+name to wrong place in results block gerard.vermeulen
2024-01-22 18:15 ` Ihor Radchenko
2024-01-22 18:50   ` gerard.vermeulen [this message]
2024-01-22 18:59     ` Ihor Radchenko
2024-01-23  8:34       ` [PATCH] Make an org-lint warning more helpful gerard.vermeulen
2024-01-24 15:49         ` Ihor Radchenko
2024-01-23 13:55       ` [BUG] org-lint tells to move #+name to wrong place in results block gerard.vermeulen
2024-01-25 12:41         ` [BUG] ox-latex produces broken references to src code listings without caption (was: [BUG] org-lint tells to move #+name to wrong place in results block) Ihor Radchenko
2024-01-26 11:04           ` gerard.vermeulen

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=429d681f72b1b13d81f24836017929d7@posteo.net \
    --to=gerard.vermeulen@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \
    /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

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).