From 03aae6bd07e9f156ca3497c7862e3a89d57708c3 Mon Sep 17 00:00:00 2001 From: Thomas Dye Date: Wed, 11 Jan 2012 15:38:36 -0700 Subject: [PATCH] * doc/org.texi: #+RESULTS now user-configurable --- doc/org.texi | 17 ++++++++++++----- 1 file changed, 12 insertions(+), 5 deletions(-) diff --git a/doc/org.texi b/doc/org.texi index a9f0139e0..222935839 100644 --- a/doc/org.texi +++ b/doc/org.texi @@ -12629,17 +12629,24 @@ of tangled code files. @section Evaluating code blocks @cindex code block, evaluating @cindex source code, evaluating +@cindex #+RESULTS Code blocks can be evaluated@footnote{Whenever code is evaluated there is a potential for that code to do harm. Org mode provides safeguards to ensure that code is only evaluated after explicit confirmation from the user. For information on these safeguards (and on how to disable them) see @ref{Code evaluation security}.} and the results of evaluation optionally placed in the -Org mode buffer. By default, the evaluation facility is only enabled for -Lisp code blocks specified as @code{emacs-lisp}. However, source code blocks -in many languages can be evaluated within Org mode (see @ref{Languages} for a -list of supported languages and @ref{Structure of code blocks} for -information on the syntax used to define a code block). +Org mode buffer. The results of evaluation are placed following a line that +begins by default with @code{#+RESULTS} and optionally a cache identifier +and/or the name of the evaluated code block. The default value of +@code{#+RESULTS} can be changed with the customizable variable +@code{org-babel-results-keyword}. + +By default, the evaluation facility is only enabled for Lisp code blocks +specified as @code{emacs-lisp}. However, source code blocks in many languages +can be evaluated within Org mode (see @ref{Languages} for a list of supported +languages and @ref{Structure of code blocks} for information on the syntax +used to define a code block). @kindex C-c C-c There are a number of ways to evaluate code blocks. The simplest is to press