Re: [O] [PATCH] Re: Capitalisation and good taste ?

2012-01-11 Thread Eric Schulte
Fantastic, I've just applied this patch, Thanks

t...@tsdye.com (Thomas S. Dye) writes:

> Aloha all,
>
> The attached patch to the manual includes information on the RESULTS
> keyword.
>
> All the best,
> Tom
>
>
>
> Eric Schulte  writes:
>
>>>
>>> I'm going to push up a patch which will change to inserting #+RESULTS:
>>> by default as well as a user-configurable variable which can be used to
>>> customize this behavior.
>>
>> Done.  This variable is named `org-babel-results-keyword'
>>
>> ,
>> | org-babel-results-keyword's value is "RESULTS"
>> | 
>> | Documentation:
>> | Keyword used to name results generated by code blocks.
>> | Should be either RESULTS or NAME however any capitalization may
>> | be used.
>> | 
>> | You can customize this variable.
>> | 
>> | [back]
>> `
>>
>> Best,

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/



[O] [PATCH] Re: Capitalisation and good taste ?

2012-01-11 Thread Thomas S. Dye
Aloha all,

The attached patch to the manual includes information on the RESULTS
keyword.

All the best,
Tom

>From 7fbabd20ed1477e706633945c98400ee48fb0ab2 Mon Sep 17 00:00:00 2001
From: Thomas Dye 
Date: Wed, 11 Jan 2012 11:23:19 -1000
Subject: [PATCH] * doc/org.texi: #+RESULTS now user-configurable

---
 doc/org.texi |   17 -
 1 files changed, 12 insertions(+), 5 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index a9f0139..2229358 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
-- 
1.7.5.4


Eric Schulte  writes:

>>
>> I'm going to push up a patch which will change to inserting #+RESULTS:
>> by default as well as a user-configurable variable which can be used to
>> customize this behavior.
>
> Done.  This variable is named `org-babel-results-keyword'
>
> ,
> | org-babel-results-keyword's value is "RESULTS"
> | 
> | Documentation:
> | Keyword used to name results generated by code blocks.
> | Should be either RESULTS or NAME however any capitalization may
> | be used.
> | 
> | You can customize this variable.
> | 
> | [back]
> `
>
> Best,

-- 
Thomas S. Dye
http://www.tsdye.com