Header arguments: clarify that `:exports' is only applicable to blocks, not inline code * doc/org.texi (Exporting code blocks): add clarification; relevant for blocks ony. * doc/org.texi (exports): add clarification; relevant for blocks only. The documentation change resulted from the expectation that `:exports' could be used with inline code blocks, which is not the case. Clarification was added to avoid future confusion on this Babel block specific header argument. TINYCHANGE From d92c30116602a97f2b11684cf5c66de3972d147b Mon Sep 17 00:00:00 2001 From: John Henderson Date: Fri, 14 Mar 2014 10:29:33 -0500 Subject: [PATCH] clarified documentation for :exports; only applicable to blocks, not inline code --- doc/org.texi | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/org.texi b/doc/org.texi index 93d5fd2..04be009 100644 --- a/doc/org.texi +++ b/doc/org.texi @@ -13828,7 +13828,8 @@ results of code block evaluation. For information on exporting code block bodies, see @ref{Literal examples}. The @code{:exports} header argument can be used to specify export -behavior: +behavior (note that these arguments are only relevant for code blocks, not +inline code): @subsubheading Header arguments: @@ -14831,7 +14832,8 @@ which the link does not point. @cindex @code{:exports}, src header argument The @code{:exports} header argument specifies what should be included in HTML -or @LaTeX{} exports of the Org mode file. +or @LaTeX{} exports of the Org mode file. Note that the @code{:exports} +option is only relevant for code blocks, not inline code. @itemize @bullet @item @code{code} -- 1.9.0