emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Torsten Anders <torsten.anders@beds.ac.uk>
To: Org-mode <emacs-orgmode@gnu.org>
Subject: [org-babel] switching off (re-)evaluation of code blocks during Org export
Date: Mon, 21 Nov 2011 16:37:13 +0000	[thread overview]
Message-ID: <42D129CE-5B0E-4793-B7CB-49A49D34217C@beds.ac.uk> (raw)

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. 

Thank you! 

Best wishes,
Torsten

--
Dr Torsten Anders
Course Leader, Music Technology
University of Bedfordshire
Park Square, Room A315
torsten.anders@beds.ac.uk
http://strasheela.sourceforge.net
http://www.torsten-anders.de

             reply	other threads:[~2011-11-21 16:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21 16:37 Torsten Anders [this message]
2011-11-21 17:26 ` [org-babel] switching off (re-)evaluation of code blocks during Org export Sebastien Vauban
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=42D129CE-5B0E-4793-B7CB-49A49D34217C@beds.ac.uk \
    --to=torsten.anders@beds.ac.uk \
    --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).