ndwarshuis
/
org-mode
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

org.texi: Fix typo 

* doc/org.texi (Exporting code blocks): Fix typo.
This commit is contained in:
Nicolas Goaziou 2016-11-14 08:43:08 +01:00
parent 3b5ce449c4
commit 047451c29d
1 changed files with 7 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/org.texi
View File

@ -14945,20 +14945,19 @@ Neither the code block nor its results will be exported.
@end table @end table
@vindex org-export-use-babel @vindex org-export-use-babel
It is possible to inhibit the evaluation of code blocks and ignore header 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 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 @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 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 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. 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 For this reason it is often better to set @code{:eval never-export} to
code evaluation but still allow headers to be honored. It is also possible prevent code evaluation but still allow headers to be honored. It is also
to set this variable to @code{inline-only}. In that case, only inline code possible to set this variable to @code{inline-only}. In that case, only
blocks will be evaluated, in order to insert their results. Non-inline code inline code blocks will be evaluated, in order to insert their results.
blocks are assumed to have their results already inserted in the buffer by Non-inline code blocks are assumed to have their results already inserted in
manual evaluation. This setting is useful to avoid expensive recalculations the buffer by manual evaluation. This setting is useful to avoid expensive
during export, not to provide security. recalculations during export, not to provide security.
Code blocks in commented subtrees (@pxref{Comment lines}) are never evaluated Code blocks in commented subtrees (@pxref{Comment lines}) are never evaluated
on export. However, code blocks in subtrees excluded from export on export. However, code blocks in subtrees excluded from export