From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: Inline code :results replace not working
Date: Mon, 10 Nov 2014 09:40:11 +0000 [thread overview]
Message-ID: <oluppcve6mc.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 8661enxvfi.fsf@example.com
Hi
Sebastien Vauban <sva-news@mygooglest.com> writes:
> Nicolas Goaziou wrote:
>> Hello,
>>
>> mcg <giepen.m@googlemail.com> writes:
>>
>>> I use inline code for simple calculations to insert numeric results into
>>> text apart from "normal" code blocks for more complex calculations and
>>> graphics (all in R).
>>>
>>>
>>> The :results replace option is not working for inline code, even if I
>>> explicitly set it in the code block. So I get
>>>
>>> #+PROPERTY: session *R*
>>>
>>> #+begin_src R :results replace value
>>> 2+3
>>> #+end_src
>>>
>>> #+RESULTS:
>>> : 5
>>>
>>> src_R[:results replace value]{2+3} =5= =5= =5= =5= =5= =5=
>>>
>>> I would really like to have numeric outcome in the buffer (not only
>>> minibuffer upon evaluation) but also evaluate the whole buffer when
>>> exporting to have everything updated.
>>>
>>> What is the problem here? For now I would have to
>>> - evaluate only on export and keep :results silent
>>> - evaluate all manually - meaning I get repeated results if I call
>>> org-evaluate buffer
>>
>> :results replace is not implemented (yet?) for inline source blocks.
>
> For me, that's the correct behavior, as inline code blocks are *only
> expected to be evaluated during export*.
>
I disagree here. As limiting the use of inline code to
eval-on-export-only renders all the org-babel-execute-subtree and
related functionality useless.
Regards,
Andreas
next prev parent reply other threads:[~2014-11-10 9:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 10:01 Inline code :results replace not working mcg
2014-11-08 21:27 ` Nicolas Goaziou
2014-11-10 9:21 ` Sebastien Vauban
2014-11-10 9:40 ` Andreas Leha [this message]
2014-11-10 10:27 ` Sebastien Vauban
2014-11-10 10:56 ` Andreas Leha
2014-11-10 11:16 ` Sebastien Vauban
2014-11-10 11:42 ` Andreas Leha
2014-11-10 16:23 ` Charles C. Berry
2014-11-10 17:03 ` Ista Zahn
2014-11-10 20:04 ` Grant Rettke
2014-11-10 20:45 ` Thomas S. Dye
2014-11-10 21:26 ` Grant Rettke
2014-11-11 1:53 ` Ista Zahn
2014-11-11 14:37 ` Grant Rettke
2014-11-13 18:40 ` Michael
2014-11-14 15:11 ` Grant Rettke
2014-11-12 9:03 ` Sebastien Vauban
2014-11-12 17:26 ` Charles Berry
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=oluppcve6mc.fsf@med.uni-goettingen.de \
--to=andreas.leha@med.uni-goettingen.de \
--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
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).