From: Ihor Radchenko <yantar92@posteo.net>
To: Tom Gillespie <tgbugs@gmail.com>, Bastien <bzg@gnu.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [BUG] inline src blocks in caption of not-inline src blocks do not execute
Date: Wed, 16 Aug 2023 09:57:10 +0000 [thread overview]
Message-ID: <87v8dfnwcp.fsf@localhost> (raw)
In-Reply-To: <CA+G3_PM2aV1jGe-sQkL0vomq-RNGc5h1BU=aEK7vw4QPnXNZkg@mail.gmail.com>
Tom Gillespie <tgbugs@gmail.com> writes:
>> It was a slip when the patch was applied.
>> May you please explain more about {{{results(=value=)}}} problem?
>> Isn't it sufficient to do src_elisp[:results verbatim]{'value} {{{results(=value=)}}}?
>
> The issue is the opposite I think. Currently the default value (i.e. absent)
> for :results does not produce {{{results(value)}}} as suggested, and instead
> producers {{{results(=value=)}}}. ...
>
> It looks like there used to be an option [:results wrap] which was deprecated
> a _very_ long time ago. [:results drawer] replaced that, and while there is
> some confusion about the name (because there is no actual drawer in an
> inline result) the behavior was meant to replace the old :results wrap behavior
> where the name does make sense since {{{results(value)}}} do "wrap" the value.
Thanks!
In addition, the docstring of `org-babel-insert-result' says
drawer -- results are added directly to the Org file as with
"raw", but are wrapped in a RESULTS drawer or results
macro, allowing them to later be replaced or removed
automatically.
But not in the manual:
‘drawer’
Result wrapped in a ‘RESULTS’ drawer. Useful for containing ‘raw’
or ‘org’ results for later scripting and automated processing.
Usage example: ‘:results value drawer’.
Also, removal of :results wrap seemingly missed the inline src block use
case: https://list.orgmode.org/orgmode/876271cjpb.fsf@bzg.ath.cx/
Bastien, may you comment?
:results drawer feels confusing for inline src blocks.
--
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>
next prev parent reply other threads:[~2023-08-16 9:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 7:50 [BUG] inline src blocks in caption of not-inline src blocks do not execute Tom Gillespie
2023-08-14 8:01 ` Ihor Radchenko
2023-08-14 8:59 ` Tom Gillespie
2023-08-16 3:31 ` Tom Gillespie
2023-08-16 8:09 ` Ihor Radchenko
2023-08-16 9:01 ` Tom Gillespie
2023-08-16 9:22 ` Ihor Radchenko
2023-08-16 9:36 ` Tom Gillespie
2023-08-16 9:57 ` Ihor Radchenko [this message]
2024-05-11 7:49 ` Ihor Radchenko
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=87v8dfnwcp.fsf@localhost \
--to=yantar92@posteo.net \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=tgbugs@gmail.com \
/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).