Re: [PATCH] small improvements to info page, Working with source code; add TINYCHANG

[Joe Riel <joer@san.rr.com>]

[-- Attachment #1: Type: text/plain, Size: 450 bytes --]

On Sat, 12 Sep 2015 11:50:23 -0700
Joe Riel <joer@san.rr.com> wrote:

> The attached two patches make small improvements to
> the "Working with source code".  
> 
> This is my first time submitting patches to org, it's
> not entirely clear that I'm doing this correctly
> (i.e. sending them to the correct place).

The attached patches replace the previous.
The patches are identical, these add TINYCHANGE to the
commit messages.

 



-- 
Joe Riel


[-- Attachment #2: 0001-doc-org.texi-Rewrite-paragraph.patch --]
[-- Type: text/x-patch, Size: 1335 bytes --]

From 358ec72642b091b0cc8e8ce87d5525f2dbd1e8ec Mon Sep 17 00:00:00 2001
From: Joe Riel <jriel@maplesoft.com>
Date: Sat, 12 Sep 2015 11:30:06 -0700
Subject: [PATCH 1/3] doc/org.texi: Rewrite paragraph

doc/org.texi (Evaluating code blocks):

Rewrite paragraph to state where to find information on enabling other
languages.  Without this, it isn't clear where to look.

TINYCHANGE.
---
 doc/org.texi | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index ac7d3a4..1e67b62 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -14972,10 +14972,9 @@ and/or the name of the evaluated code block.  The default value of
 @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).
+specified as @code{emacs-lisp}.  See @ref{Languages} to enable other
+supported languages.  See @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
-- 
2.1.4


[-- Attachment #3: 0002-doc-org.texi-add-link-to-relevant-chapter.patch --]
[-- Type: text/x-patch, Size: 1206 bytes --]

From 29679d5e5854e9a2ff0e41af92c451ccdcd82f73 Mon Sep 17 00:00:00 2001
From: Joe Riel <jriel@maplesoft.com>
Date: Sat, 12 Sep 2015 11:36:50 -0700
Subject: [PATCH 2/3] doc/org.texi: add link to relevant chapter

* doc/org.texi (Exporting code blocks) add link to Exporting

Coming into this section without having read the chapter 12
is pretty confusing.  The link is helpful.

TINYCHANGE.
---
 doc/org.texi | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/org.texi b/doc/org.texi
index 1e67b62..c630c7a 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -14851,7 +14851,8 @@ of code block evaluation, @emph{both} the code and the results of code block
 evaluation, or @emph{none}.  For most languages, the default exports code.
 However, for some languages (e.g., @code{ditaa}) the default exports the
 results of code block evaluation.  For information on exporting code block
-bodies, see @ref{Literal examples}.
+bodies, see @ref{Literal examples}.  For information on exporting
+parts of Org documents, see @ref{Exporting}.
 
 The @code{:exports} header argument can be used to specify export
 behavior (note that these arguments are only relevant for code blocks, not
-- 
2.1.4