From: Nick Dokos <nicholas.dokos@hp.com>
To: "Cook, Malcolm" <MEC@stowers.org>
Cc: "'andreas.leha@med.uni-goettingen.de'"
<andreas.leha@med.uni-goettingen.de>,
nicholas.dokos@hp.com,
"'emacs-orgmode@gnu.org'" <emacs-orgmode@gnu.org>
Subject: Re: HOWTO?: export without (re)eval-ing src blocks (was? disable automatic source block evaluation but allow manual)
Date: Fri, 16 Sep 2011 13:00:56 -0400 [thread overview]
Message-ID: <6251.1316192456@alphaville.americas.hpqcorp.net> (raw)
In-Reply-To: Message from "Cook, Malcolm" <MEC@stowers.org> of "Fri, 16 Sep 2011 11:49:38 CDT." <2C40E43D1F7A56408C4463FD245DDDF9841B3410@EXCHMB-02.stowers-institute.org>
[forgot to cc: the list]
Cook, Malcolm <MEC@stowers.org> wrote:
> I would like to be able to export a buffer as HTML, LaTex,
> what-have-you without having to re-evaluate any source blocks, and
> without having to modify the :eval tag in any source header blocks.
>
> Is there any way to accomplish this via hooks, flags, appropriate
> function calls?
> ...
Maybe this:
,----
| org-export-babel-evaluate is a variable defined in `ob-exp.el'.
| Its value is t
|
| This variable is safe as a file local variable if its value
| satisfies the predicate `(lambda (x) (eq x nil))'.
|
| Documentation:
| Switch controlling code evaluation during export.
| When set to nil no code will be evaluated as part of the export
| process.
`----
Nick
next prev parent reply other threads:[~2011-09-16 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 16:49 HOWTO?: export without (re)eval-ing src blocks (was? disable automatic source block evaluation but allow manual) Cook, Malcolm
2011-09-16 17:00 ` Nick Dokos [this message]
2011-09-16 17:35 ` Cook, Malcolm
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=6251.1316192456@alphaville.americas.hpqcorp.net \
--to=nicholas.dokos@hp.com \
--cc=MEC@stowers.org \
--cc=andreas.leha@med.uni-goettingen.de \
--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).