branch: externals/org
commit 53c28d27d07d7338267eb217d161fdffb71b7796
Author: Ihor Radchenko <[email protected]>
Commit: Ihor Radchenko <[email protected]>
org-manual: Document when code blocks with :eval yes are not evaluated on
export
* doc/org-manual.org (Exporting Code Blocks): Explain that :exports
code/none does not evaluate code even with :eval yes, unless the code
uses session.
Reported-by: Pedro Andres Aranda Gutierrez <[email protected]>
---
doc/org-manual.org | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index 17ca72e9b4..3fe889931c 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -19555,6 +19555,11 @@ To stop Org from evaluating code blocks for greater
security, set the
~org-export-use-babel~ variable to ~nil~, but understand that header
arguments will have no effect.
+If results of evaluation are not marked for export (=:exports code= or
+=:exports none=), Org will not evaluate them, even for =:eval yes=.
+The only exception is when a code block uses =:session= - such blocks
+are evaluated according to their =:eval= header argument.
+
Turning off evaluation comes in handy when batch processing. For
example, markup languages for wikis, which have a high risk of
untrusted code. Stopping code block evaluation also stops evaluation
