From: Eric Schulte <schulte.eric@gmail.com>
To: Torsten Anders <torsten.anders@beds.ac.uk>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [org-babel] switching off (re-)evaluation of code blocks during Org export
Date: Mon, 21 Nov 2011 18:23:31 -0700 [thread overview]
Message-ID: <87aa7plzl8.fsf@gmail.com> (raw)
In-Reply-To: <2A2CA71C-50E6-4533-BD40-2D879EF3BBCC@beds.ac.uk> (Torsten Anders's message of "Tue, 22 Nov 2011 00:13:03 +0000")
Hi Torsten,
Torsten Anders <torsten.anders@beds.ac.uk> writes:
> Dear Sebastien and Eric,
>
> Thanks a lot for your kind replies. However, this is not yet quite what I am after.
>
> I want to be able to manually execute each code block, but not
> automatically whenever the whole document is rendered. So, I would
> always switch on/off "eval never". Hm...
>
I've just pushed up a patch which adds a new option to the "eval" header
argument. Setting eval to "non-export" will now allow interactive
evaluation, but will inhibit code block evaluation during export. This
should address your need as I understand it.
>
> I will try out the ":cache" header argument. However, again this does
> not work so well, because for the languages I am using the :file
> argument does not work very well (I have to manually change
> extensions, so I include the resulting file links by hand anyway and
> set :results to silent.
>
> So, I it sounds like few org-babel users is really running larger
> applications in their code blocks which can delay the export of the
> whole document considerably.
>
I would not jump to that conclusion. I have used babel code blocks to
cache the results of very long running results, however between the
:cache header argument and the ability to manually disassociate
generated results from code blocks I have not had any problems
inhibiting execution during export.
Best -- Eric
>
> Anyway, thanks a lot for your feedback.
>
> Best wishes,
> Torsten
>
>
>
>
--
Eric Schulte
http://cs.unm.edu/~eschulte/
next prev parent reply other threads:[~2011-11-22 1:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 0:13 [org-babel] switching off (re-)evaluation of code blocks during Org export Torsten Anders
2011-11-22 1:23 ` Eric Schulte [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2011-11-21 16:37 Torsten Anders
2011-11-21 17:26 ` Sebastien Vauban
2011-11-21 17:34 ` 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=87aa7plzl8.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=torsten.anders@beds.ac.uk \
/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).