Hello, Eric Schulte <eric.schu...@gmx.com> writes:
>> It's out of exporter's scope. > > I disagree. The current exporter conforms to the value of the :results > header argument (e.g., silent, replace, append, etc...) when executing > code blocks during export. I see no reason why the new exporter should > not as well. The new exporter conforms to the output of `org-export-blocks-preprocess'. It doesn't pay attention to header arguments. > Hmm, in light of this description it seems that the new export /should/ > have the same behavior WRT code block execution as the current > exporter. If not I wonder if a complete minimal example could be > provided. Martyn Jago provided one in this thread. Here it is: --8<---------------cut here---------------start------------->8--- * Test #+begin_src emacs-lisp # :exports both ;; Add two numbers (+ 2 3) #+end_src #+results: : 5 --8<---------------cut here---------------end--------------->8--- Regards, -- Nicolas Goaziou
