From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [org-babel] switching off (re-)evaluation of code blocks during Org export
Date: Mon, 21 Nov 2011 18:26:30 +0100 [thread overview]
Message-ID: <80fwhhidyx.fsf@somewhere.org> (raw)
In-Reply-To: 42D129CE-5B0E-4793-B7CB-49A49D34217C@beds.ac.uk
Hi Torsten,
Torsten Anders wrote:
> Dear Org-Babel developers,
>
> When I am exporting an *.org buffer to, say, HTML or PDF (via Latex) the
> code blocks of at least some languages are executed during the export
> process. (Has this always been like that, I noticed this for the first
> time?)
>
> I would like to switch that off completely. I prefer evaluating code blocks
> individually to check their results. Also, many of by code blocks run
> substantial programs which slow down the export process considerably.
>
> I could not find an option to switch this off in the documentation.
> Apologies if I missed something obvious. I assume it is there somewhere, but
> I could not find it.
#+PROPERTY: eval never
does inhibit evaluation of the code blocks.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2011-11-21 17:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 16:37 [org-babel] switching off (re-)evaluation of code blocks during Org export Torsten Anders
2011-11-21 17:26 ` Sebastien Vauban [this message]
2011-11-21 17:34 ` Eric Schulte
-- strict thread matches above, loose matches on Subject: below --
2011-11-22 0:13 Torsten Anders
2011-11-22 1:23 ` Eric Schulte
2011-11-22 9:46 ` Sebastien Vauban
2011-11-22 14:02 ` Eric Schulte
2011-11-22 17:15 ` Bernt Hansen
2011-11-22 17:31 ` Eric Schulte
2011-11-27 20:12 ` Torsten Anders
2011-11-28 7:13 ` Eric Schulte
2011-11-28 10:01 ` Torsten Anders
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=80fwhhidyx.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).