From: "Eric Schulte" <schulte.eric@gmail.com>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: disable automatic source block evaluation but allow manual
Date: Thu, 16 Dec 2010 07:54:21 -0700 [thread overview]
Message-ID: <87ipytn4yq.fsf@gmail.com> (raw)
In-Reply-To: <801v5hvkv1.fsf@missioncriticalit.com> ("Sébastien Vauban"'s message of "Thu, 16 Dec 2010 15:43:46 +0100")
Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:
>>> I guess one possibility would be to have a header argument
>>> (update-results-when-exporting) which, if set, would update all results
>>> in the org buffer and export then.
>>
>> This can also be accomplished using an export hook. e.g.
>>
>>
>
> Thanks Eric for this. Though it is not yet *exactly* what I meant: here,
> buffer is executed twice, once just before exporting (thru the hook) and once
> when exporting.
>
> Hence:
>
> - The results still may defer: date example that I gave previously in this
> thread, but as well results of SQL code execution that would have
> side-effects, etc... Not completely in sync'.
>
> - Regarding performance, it consumes twice as much time...
>
> Would it be possible, then, to avoid executing the buffer when exporting (only
> keeping it, once, in the export hook)?
Yes, this should be possible through setting the :cache header argument
on a buffer-wide basis, and calling `org-babel-execute-buffer' with a
prefix argument (which forces re-evaluation in the face of caching).
(add-hook 'org-export-first-hook (lambda () (org-babel-execute-buffer t)))
Best -- Eric
next prev parent reply other threads:[~2010-12-16 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 8:50 disable automatic source block evaluation but allow manual Andreas Leha
2010-12-16 9:48 ` Sébastien Vauban
2010-12-16 13:48 ` Andreas Leha
2010-12-16 14:08 ` Rainer M Krug
2010-12-16 14:16 ` Eric Schulte
2010-12-16 14:43 ` Sébastien Vauban
2010-12-16 14:54 ` Eric Schulte [this message]
2010-12-16 13:23 ` 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=87ipytn4yq.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.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).