From: Alain.Cochard@unistra.fr
To: "Rudolf Adamkovič" <salutis@me.com>
Cc: alain.cochard@unistra.fr, Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Confused about source code blocks evaluation when exporting
Date: Thu, 14 Jul 2022 08:48:03 +0200 [thread overview]
Message-ID: <25295.48163.708736.350014@gargle.gargle.HOWL> (raw)
In-Reply-To: <m25yk0cjnh.fsf@me.com>
Rudolf Adamkovič writes on Thu 14 Jul 2022 08:06:
> Alain.Cochard@unistra.fr writes:
>
> > Org evaluates source code blocks in an Org file during export.
>
> I have just tried to export the following document:
>
> #+begin_src emacs-lisp :exports both
> (+ 1 1)
> #+end_src
>
> The exported HTML file contains the expression '(+ 1 1)' along with
> '2', its value. It follows that Emacs does evaluate source blocks
> on export.
Yes, but it is because you used ':exports both'. Without that, I only
have '(+ 1 1)'. Would you not still speak about the "exported HTML
file"?
a.
(Thanks for the other precisions.)
--
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 ]
prev parent reply other threads:[~2022-07-14 6:52 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
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 [this message]
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=25295.48163.708736.350014@gargle.gargle.HOWL \
--to=alain.cochard@unistra.fr \
--cc=emacs-orgmode@gnu.org \
--cc=salutis@me.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).