Hello, Eric Schulte <schulte.e...@gmail.com> writes:
> If I understand correctly, I think ":export both :results none" should > have the desired effect of executing the code block, not inserting the > results, and keeping the code block itself in place. AFAICT, ":export both :results none" combination doesn't seem to produce the desired outcome with the example file. Note that the feature is only needed for elisp, since it is the only language able to modify the buffer containing the source code. > If you want to run emacs lisp at export time but don't want the code or > the results, maybe it would be a more natural fit for a filter > function? I think the OP wants (org-babel-execute-buffer) and (org-export-execute-babel-code) to behave the same in this specific situation. So, it's not export-specific. To put it differently, he wants to disable code replacement with value (which is specific to the export part of Babel). Regards, -- Nicolas Goaziou
