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

From: gerard.vermeulen@posteo.net
To: Emacs orgmode <emacs-orgmode@gnu.org>
Subject: [BUG] org-lint tells to move #+name to wrong place in results block
Date: Mon, 22 Jan 2024 17:47:50 +0000	[thread overview]
Message-ID: <60f395fcacacdc6a7d9de3cd7a00032b@posteo.net> (raw)

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"
re-evalution makes "#+name: OUT" disappear.

#+header: :wrap "src emacs-lisp"
#+name: IN
#+begin_src emacs-lisp
3
#+end_src

#+name: OUT
#+RESULTS: IN
#+begin_src emacs-lisp
3
#+end_src

Listing [[IN]] produces listing [[OUT]], clicking each link in Org
jumps to the linked block, TAB-bing on "#+name: OUT" folds the
block, but exporting says:  Unable to resolve the link "OUT".

Org mode version 9.7-pre (release_9.6.17-1081-g83696b)

FR: would it be possible to resolve such links?

Regards -- Gerard

next             reply	other threads:[~2024-01-22 17:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 17:47 gerard.vermeulen [this message]
2024-01-22 18:15 ` [BUG] org-lint tells to move #+name to wrong place in results block Ihor Radchenko
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=60f395fcacacdc6a7d9de3cd7a00032b@posteo.net \
    --to=gerard.vermeulen@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    /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).