|
@@ -14945,20 +14945,19 @@ Neither the code block nor its results will be exported.
|
|
|
@end table
|
|
|
|
|
|
@vindex org-export-use-babel
|
|
|
-
|
|
|
It is possible to inhibit the evaluation of code blocks and ignore header
|
|
|
arguments during export. Setting the @code{org-export-use-babel} variable to
|
|
|
@code{nil} will ensure that no code blocks are evaluated as part of the
|
|
|
export process. This can be useful in situations where potentially untrusted
|
|
|
Org files are exported in an automated fashion, for example when Org is used
|
|
|
as the markup language for a wiki. No header arguments will be processed.
|
|
|
-For this reason it is often better to set `:eval never-export' to prevent
|
|
|
-code evaluation but still allow headers to be honored. It is also possible
|
|
|
-to set this variable to @code{inline-only}. In that case, only inline code
|
|
|
-blocks will be evaluated, in order to insert their results. Non-inline code
|
|
|
-blocks are assumed to have their results already inserted in the buffer by
|
|
|
-manual evaluation. This setting is useful to avoid expensive recalculations
|
|
|
-during export, not to provide security.
|
|
|
+For this reason it is often better to set @code{:eval never-export} to
|
|
|
+prevent code evaluation but still allow headers to be honored. It is also
|
|
|
+possible to set this variable to @code{inline-only}. In that case, only
|
|
|
+inline code blocks will be evaluated, in order to insert their results.
|
|
|
+Non-inline code blocks are assumed to have their results already inserted in
|
|
|
+the buffer by manual evaluation. This setting is useful to avoid expensive
|
|
|
+recalculations during export, not to provide security.
|
|
|
|
|
|
Code blocks in commented subtrees (@pxref{Comment lines}) are never evaluated
|
|
|
on export. However, code blocks in subtrees excluded from export
|