Re: [O] org-export-babel-evaluate and :exports none

[Ista Zahn]

On Fri, Feb 22, 2013 at 3:49 PM, Achim Gratz <address@hidden> wrote:
> 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).

FWIW, I have not experienced this bug. I always set
org-export-babel-evaluate to nil, and this has always had the desired
effect of preventing babel evaluation on export.

Best,
Ista

>
>> 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
>
>