emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Thomas S. Dye" <tsd@tsdye.com>
To: nicholas.dokos@hp.com
Cc: Ken.Williams@thomsonreuters.com, emacs-orgmode@gnu.org
Subject: [Patch] Documentation, was Re:  Spurious source-code output?
Date: Thu, 5 May 2011 08:28:02 -1000	[thread overview]
Message-ID: <F1CDDC52-F963-4811-81B3-8D5B09945E43@tsdye.com> (raw)
In-Reply-To: <607.1304617504@alphaville.dokosmarshall.org>

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

Hi Nick,

Thanks for fixing the documentation link.

Here is a patch that adds a reference to language-specific header  
arguments.

All the best,
Tom


[-- Attachment #2: 0001-Refer-to-language-specific-Babel-header-arguments.patch --]
[-- Type: application/octet-stream, Size: 860 bytes --]

From 825fe69d493dd2e7eef414b85340e8e27400f78d Mon Sep 17 00:00:00 2001
From: Tom Dye <tsd@tsdye.com>
Date: Thu, 5 May 2011 08:24:24 -1000
Subject: [PATCH] Refer to language specific Babel header arguments

---
 doc/org.texi |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index 7142ce0..98842ba 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -11885,6 +11885,9 @@ The following header arguments are defined:
 * eval::                        Limit evaluation of specific code blocks
 @end menu
 
+Additional header arguments are defined on a language-specific basis, see
+@ref{Languages}. 
+
 @node var, results, Specific header arguments, Specific header arguments
 @subsubsection @code{:var}
 The @code{:var} header argument is used to pass arguments to code blocks.
-- 
1.7.1


[-- Attachment #3: Type: text/plain, Size: 1530 bytes --]




On May 5, 2011, at 7:45 AM, Nick Dokos wrote:

> Thomas S. Dye <tsd@tsdye.com> wrote:
>
>> Hi Nick,
>>
>> Without claiming to be a babel expert, :results graphics is a  
>> language-
>> specific option used for e.g. R code blocks.  You can find it
>> documented in the appropriate language-specific sections.
>>
>
> OK - thanks for the clarification! It might be a good idea to note
> (perhaps in section 14.8.2, "Specific header arguments", or perhaps  
> its
> parent?) that individual languages might provide extensions to the
> standard header args. Also, the link in the manual (section 14.7,  
> "Languages")
> to language-specific documentation should probably be changed to
>
>   http://orgmode.org/worg/org-contrib/babel/languages.html
>
> which provides some useful context. The current link just takes you to
> the directory listing. Trivial patch for the latter problem is  
> appended.
>
> Thanks,
> Nick
>
> diff --git a/doc/org.texi b/doc/org.texi
> index a0f6638..8cf5535 100644
> --- a/doc/org.texi
> +++ b/doc/org.texi
> @@ -11639,7 +11639,7 @@ Code blocks in the following languages are  
> supported.
>
> Language-specific documentation is available for some languages.  If
> available, it can be found at
> -@uref{http://orgmode.org/worg/org-contrib/babel/languages}.
> +@uref{http://orgmode.org/worg/org-contrib/babel/languages.html}.
>
> The @code{org-babel-load-languages} controls which languages are  
> enabled for
> evaluation (by default only @code{emacs-lisp} is enabled).  This  
> variable can


  reply	other threads:[~2011-05-05 18:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-05 15:24 Spurious source-code output? Ken.Williams
2011-05-05 15:37 ` Nick Dokos
2011-05-05 15:40   ` Ken.Williams
2011-05-05 15:55     ` Nick Dokos
2011-05-05 17:07       ` Thomas S. Dye
2011-05-05 17:45         ` Nick Dokos
2011-05-05 18:28           ` Thomas S. Dye [this message]
2011-05-05 19:09             ` [Patch] Documentation, was " Nick Dokos
2011-05-05 19:31               ` Thomas S. Dye
2011-05-05 19:48                 ` Nick Dokos
2011-05-05 21:03               ` Nick Dokos
2011-05-05 20:52             ` Eric Schulte
2011-05-05 21:51             ` Nick Dokos

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=F1CDDC52-F963-4811-81B3-8D5B09945E43@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=Ken.Williams@thomsonreuters.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.com \
    /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).