Tom Gillespie <tgb...@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....@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>
