Browse Source

org.texi: fix noweb-ref property, clarify `Exporting code blocks'

* org.texi: The example in the `noweb-ref' node now uses the
  :header-arg: property to declare the :noweb-ref reference.  The
  `Exporting code blocks' node is edited to more carefully warn users
  of the consequences of setting `org-export-use-babel' to `nil'.
Charles Berry 8 years ago
parent
commit
fed1cf1c99
1 changed files with 6 additions and 3 deletions
  1. 6 3
      doc/org.texi

+ 6 - 3
doc/org.texi

@@ -15003,8 +15003,11 @@ Org does not export the code block nor the results.
 @end table
 
 @vindex org-export-use-babel
-To stop Org from evaluating code blocks during export, set
-@code{org-export-use-babel} variable to @code{nil}.
+To stop Org from evaluating code blocks to speed exports, use the header
+argument @code{:eval never-export} (@pxref{eval}).  To stop Org from
+evaluating code blocks for greater security, set the
+@code{org-export-use-babel} variable to @code{nil}, but understand that
+header arguments will have no effect.
 
 Turning off evaluation comes in handy when batch processing.  For example,
 markup languages for wikis, which have a high risk of untrusted code.
@@ -16149,7 +16152,7 @@ file@footnote{(For the example to work, turn on the property inheritance for
  #+END_SRC
  * the mount point of the fullest disk
    :PROPERTIES:
-   :noweb-ref: fullest-disk
+   :header-args: :noweb-ref fullest-disk
    :END:
 
  ** query all mounted disks