emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: gerard.vermeulen@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:15:31 +0000	[thread overview]
Message-ID: <875xzls08s.fsf@localhost> (raw)
In-Reply-To: <60f395fcacacdc6a7d9de3cd7a00032b@posteo.net>

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?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2024-01-22 18:13 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 [this message]
2024-01-22 18:50   ` gerard.vermeulen
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=875xzls08s.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=gerard.vermeulen@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
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).