From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Riel Subject: [PATCH] small improvements to info page, Working with source code Date: Sat, 12 Sep 2015 11:50:23 -0700 Message-ID: <20150912115023.2be56657@gauss> References: <20150910222354.743ce9f2@gauss> <20150911073700.356f5760@gauss> <20150911211305.295d8ff4@gauss> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="MP_/ZrDNJtZqbJM8_VLVLQsEDxX" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36503) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zapsa-0006u2-OB for emacs-orgmode@gnu.org; Sat, 12 Sep 2015 14:50:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZapsX-0005wZ-2F for emacs-orgmode@gnu.org; Sat, 12 Sep 2015 14:50:28 -0400 Received: from cdptpa-outbound-snat.email.rr.com ([107.14.166.232]:22747 helo=cdptpa-oedge-vip.email.rr.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZapsW-0005wC-SV for emacs-orgmode@gnu.org; Sat, 12 Sep 2015 14:50:24 -0400 In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "Thomas S. Dye" Cc: emacs-orgmode@gnu.org --MP_/ZrDNJtZqbJM8_VLVLQsEDxX Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline 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). -- Joe Riel --MP_/ZrDNJtZqbJM8_VLVLQsEDxX Content-Type: text/x-patch Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=0001-doc-org.texi-Evaluating-code-blocks-Rewrite-paragrap.patch >From 2dad38f55c6c2e1dbe37eb7c5cdad94f5ed94ca9 Mon Sep 17 00:00:00 2001 From: Joe Riel Date: Sat, 12 Sep 2015 11:30:06 -0700 Subject: [PATCH 1/2] * doc/org.texi: (Evaluating code blocks) Rewrite paragraph to state where to find information on enabling other languages. --- 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 --MP_/ZrDNJtZqbJM8_VLVLQsEDxX Content-Type: text/x-patch Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=0002-doc-org.texi-Exporting-code-blocks-add-link-to-Expor.patch >From af923060170cdaba9eaa6701d0e8175837429d84 Mon Sep 17 00:00:00 2001 From: Joe Riel Date: Sat, 12 Sep 2015 11:36:50 -0700 Subject: [PATCH 2/2] * 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. --- 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 --MP_/ZrDNJtZqbJM8_VLVLQsEDxX--