From: Alain.Cochard@unistra.fr
To: alain.cochard@unistra.fr
Cc: Org Mode List <emacs-orgmode@gnu.org>,
"Fraga, Eric" <e.fraga@ucl.ac.uk>,
Greg Minshall <minshall@umich.edu>
Subject: Re: Confused about source code blocks evaluation when exporting
Date: Tue, 12 Jul 2022 23:13:49 +0200 [thread overview]
Message-ID: <25293.58381.803841.645075@gargle.gargle.HOWL> (raw)
In-Reply-To: <25293.28342.763993.795868@gargle.gargle.HOWL>
Fraga, Eric writes on Tue 12 Jul 2022 14:08:
> On Tuesday, 12 Jul 2022 at 14:53, Alain.Cochard@unistra.fr wrote:
> > So far so good. (Well almost: why does '#+RESULTS:' show 'bar' and
> > not 'foo'? After all, I'm just setting 'my-var', I'm not asking to
> > display its value. But that's incidental.)
>
> It's not incidental. By default, the results of a src block evaluation
> is the value of the src block which is typically the value returned by
> the last statement.
I guess I didn't use 'incidental' correctly. I meant it as "not my
main concern". Anyway, thank you; I could check that if I switch the
2 lines I indeed get '#+RESULTS:' to show foo'.
> You can modify this by adding
>
> :results output
>
> for instance to the begin_src line.
>
> > (test 2) Same org file. If I do 'C-c C-e l o', no question is asked,
> > no '#+RESULTS:' block is inserted, and the resulting pdf file shows:
>
> On export, the default is to export the code. If you want the results,
> you need to add
>
> :exports results
>
> or if you want both code and results,
>
> :exports both
Greg Minshall writes on Tue 12 Jul 2022 17:22:
> maybe look in the org manual for ":results" (with "value" or
> "output" as options) and ":exports" (with "code" or "results" or
> "both" as options).
Thank you both, I made progress; but the behavior is still very so
unintuitive to me. For example, I haven't found a way to have this
block:
#+begin_src emacs-lisp <arguments to be determined>
(message "foo")
(message "bar")
#+END_SRC
and have the following inserted during export:
#+RESULTS:
: foo
: bar
(after all, that is was goes into the *Messages* buffer upon
evaluation with 'C-c C-c'...)
Finally I still tend to consider that the sentence "Org evaluates
source code blocks in an Org file during export" is confusing. But
maybe that's just I who interpret this as "code evaluation is the
default behavior upon export".
Regards
--
EOST (École et Observatoire des Sciences de la Terre)
ITE (Institut Terre & Environnement) | alain.cochard@unistra.fr
5 rue René Descartes [bureau 106] | Phone: +33 (0)3 68 85 50 44
F-67084 Strasbourg Cedex, France | [ slot available for rent ]
next prev parent reply other threads:[~2022-07-12 21:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 12:53 Confused about source code blocks evaluation when exporting Alain.Cochard
2022-07-12 14:08 ` Fraga, Eric
2022-07-14 5:47 ` Rudolf Adamkovič
2022-07-12 14:22 ` Greg Minshall
2022-07-12 21:13 ` Alain.Cochard [this message]
2022-07-13 10:57 ` Fraga, Eric
2022-07-13 21:06 ` Alain.Cochard
2022-07-14 7:06 ` Fraga, Eric
2022-07-14 8:09 ` Alain.Cochard
2022-07-14 8:35 ` Fraga, Eric
2022-07-20 12:12 ` Alain.Cochard
2022-07-20 12:43 ` Fraga, Eric
2022-07-22 4:27 ` Alain.Cochard
2022-07-22 17:09 ` Fraga, Eric
2022-07-22 22:21 ` Alain.Cochard
2022-07-14 6:06 ` Rudolf Adamkovič
2022-07-14 6:48 ` Alain.Cochard
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=25293.58381.803841.645075@gargle.gargle.HOWL \
--to=alain.cochard@unistra.fr \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=minshall@umich.edu \
/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).