From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: org-export-babel-evaluate and :exports none
Date: Fri, 22 Feb 2013 21:49:45 +0100 [thread overview]
Message-ID: <87ppzsnkeu.fsf@Rainer.invalid> (raw)
In-Reply-To: 877gm33sti.fsf@gmail.com
Nicolas Goaziou writes:
> I'm just starting over because that wasn't a correct solution. I'm not
> even sure about what bug this patch fixed.
The bug was that Babel blocks were evaluated during export when
org-export-babel-evaluate was explicitly set to nil (the default value
is t).
> Anyway, it isn't org-export-babel-evaluate's job to tell when to
> evaluate a source code block.
The documentation says that its job is exactly that, if the context is
export.
--8<---------------cut here---------------start------------->8---
Documentation:
Switch controlling code evaluation during export.
When set to nil no code will be evaluated as part of the export
process.
--8<---------------cut here---------------end--------------->8---
> It may be org-babel-exp-process-buffer's.
You call org-export-execute-babel-code however, which doesn't check the
above variable.
>> BTW, the function org-export-execute-babel-code is called before it is
>> being defined. Not sure why this doesn't give a warning.
>
> Why should it? It's not a macro, after all.
Ah yes. To much C++ the last month.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2013-02-22 20:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-17 14:24 org-export-babel-evaluate and :exports none Ista Zahn
2013-02-18 18:22 ` Ista Zahn
2013-02-18 18:59 ` Jay Kerns
2013-02-18 19:20 ` Ista Zahn
2013-02-18 20:17 ` Nicolas Goaziou
2013-02-18 20:26 ` Ista Zahn
2013-02-18 20:42 ` Achim Gratz
2013-02-20 15:31 ` Nicolas Goaziou
2013-02-22 20:49 ` Achim Gratz [this message]
2013-02-22 21:42 ` Ista Zahn
2013-02-23 8:08 ` Nicolas Goaziou
2013-02-23 8:45 ` Achim Gratz
2013-02-18 20:49 ` Achim Gratz
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=87ppzsnkeu.fsf@Rainer.invalid \
--to=stromeko@nexgo.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).