From: Dan Davison <dandavison7@gmail.com>
To: Andreas Leha <andreas.leha@med.uni-goettingen.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: inline code block results
Date: Fri, 04 Feb 2011 17:11:15 +0000 [thread overview]
Message-ID: <m162szpvws.fsf@gmail.com> (raw)
In-Reply-To: <4D4C2836.5010306@med.uni-goettingen.de> (Andreas Leha's message of "Fri, 04 Feb 2011 17:24:22 +0100")
Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
> Hi all,
>
> just found out: the inline block works when I explicitly state :results
> replace.
>
> So both questions from the previous email collapse to: why is that
> necessary?
>
> Regards,
> Andreas
>
>
>
> Am 04.02.2011 17:13, schrieb Andreas Leha:
>> Hi all,
>>
>> I have two questions:
>>
>> (1) How do I get resuts from code block evaluation (e.g. a single
>> number) inline into text during (LaTeX-)export? Something like: We use
>> a level of #+call: getLevel()
>>
>> (2) Why do these two subheadings produce different output during
>> (LaTeX-)export?
>> * Test
>> ** Normal source code block
>> The number is
>> #+srcname: success_parameter_one
>> #+begin_src R :session :results value :exports results
>> tmp <- rnorm(1)
>> #+end_src
>>
>> ** Inline source code block
>> The number is src_R[:session :results value :exports results]{tmp <-
>> rnorm(1)}
Hi Andreas,
This is a bug, thanks. They should both produce the number (and no code)
in the exported material.
It bisects to d0ca215105 which is a recent commit re-working export of
inline- and regular src blocks. I believe the fix may be as below but
I'll let Eric S check that.
Note that in your inline src block :results value and :exports results
are usually unnecessary, as they are the default values for inline src
blocks.
Dan
diff --git a/lisp/ob.el b/lisp/ob.el
index b899410..3fecbbd 100644
--- a/lisp/ob.el
+++ b/lisp/ob.el
@@ -297,7 +297,7 @@ specific header arguments as well.")
"Default arguments to use when evaluating a source block.")
(defvar org-babel-default-inline-header-args
- '((:session . "none") (:results . "silent") (:exports . "results"))
+ '((:session . "none") (:results . "replace") (:exports . "results"))
"Default arguments to use when evaluating an inline source block.")
(defvar org-babel-current-buffer-properties nil
>>
>>
>> Thanks in advance!
>> Andreas
>>
>>
next prev parent reply other threads:[~2011-02-04 17:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 16:13 inline code block results Andreas Leha
2011-02-04 16:24 ` Andreas Leha
2011-02-04 17:11 ` Dan Davison [this message]
2011-02-04 17:26 ` Andreas Leha
2011-02-04 20:29 ` Eric Schulte
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=m162szpvws.fsf@gmail.com \
--to=dandavison7@gmail.com \
--cc=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).