From: Joe Riel <joer@san.rr.com>
To: Joe Riel <joer@san.rr.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] small improvements to info page, Working with source code; add TINYCHANG
Date: Sun, 13 Sep 2015 10:32:27 -0700 [thread overview]
Message-ID: <20150913103227.2e561d74@gauss> (raw)
In-Reply-To: <20150912115023.2be56657@gauss>
[-- 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
next prev parent reply other threads:[~2015-09-13 17:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 5:23 obtain ob-template.el for Babel language extension Joe Riel
2015-09-11 6:38 ` Thomas S. Dye
2015-09-11 14:37 ` Joe Riel
2015-09-11 16:03 ` Thomas S. Dye
2015-09-11 19:30 ` Marco Maggesi
2015-09-13 17:45 ` Joe Riel
2015-09-15 2:37 ` Thomas S. Dye
2015-09-16 15:43 ` Joe Riel
2015-09-12 4:13 ` Joe Riel
2015-09-12 17:15 ` Thomas S. Dye
2015-09-12 17:39 ` Joe Riel
2015-09-12 18:50 ` [PATCH] small improvements to info page, Working with source code Joe Riel
2015-09-13 17:32 ` Joe Riel [this message]
2015-09-13 18:24 ` [PATCH] small improvements to info page, Working with source code; add TINYCHANG Rasmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150913103227.2e561d74@gauss \
--to=joer@san.rr.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).