Hello, Achim Gratz <strom...@nexgo.de> writes:
> Nicolas Goaziou writes: >> I confirm the problem. It is coming from >> 12d592b73223f3b0628e10f0f627447b1a312203. I reverted it. > > Doesn't this throw the baby out with the bathtub? If anything that's an > indication that the evaluation and the exporting of a block should be > independently controllable. So either org-babel-exp-process-buffer is > not the correct function to call or it needs to take > org-export-babel-evaluate into account. I'm just starting over because that wasn't a correct solution. I'm not even sure about what bug this patch fixed. Anyway, it isn't org-export-babel-evaluate's job to tell when to evaluate a source code block. It may be org-babel-exp-process-buffer's. I asked the author of that patch to provide more information about the context so I can get a clue. > 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. Regards, -- Nicolas Goaziou
