emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Thomas S. Dye" <tsd@tsdye.com>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org
Subject: Re: [Patch] Documentation, was Re:  Spurious source-code output?
Date: Thu, 5 May 2011 09:31:09 -1000	[thread overview]
Message-ID: <AE998D6C-DF53-4D2D-9131-D917411D850F@tsdye.com> (raw)
In-Reply-To: <1364.1304622569@alphaville.dokosmarshall.org>

Ack.  There were problems earlier with my Mac Mail client and line  
breaks, IIRC, but here is the patch in-line.  I'm not sure how to make  
attachments follow specific MIME requirements.

All the best,
Tom

 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



On May 5, 2011, at 9:09 AM, Nick Dokos wrote:

> Thomas S. Dye <tsd@tsdye.com> wrote:
>
>> Hi Nick,
>>
>> Thanks for fixing the documentation link.
>>
>> Here is a patch that adds a reference to language-specific header
>> arguments.
>>
>
> I think it's still the case that attachments of MIME type
> application/octet-stream will not be recorded in patchwork.  Please  
> use
> one of the types that patchwork will recognize (text/plain is the  
> best -
> remember the Orgmode motto!) or just insert it inline.
>
> See http://thread.gmane.org/gmane.emacs.orgmode/25727.
>
> I'll add a note to that effect to org-contribute.html on Worg
> unless somebody tells me otherwise.
>
> Nick
>
>

  reply	other threads:[~2011-05-05 19:31 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           ` [Patch] Documentation, was " Thomas S. Dye
2011-05-05 19:09             ` Nick Dokos
2011-05-05 19:31               ` Thomas S. Dye [this message]
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=AE998D6C-DF53-4D2D-9131-D917411D850F@tsdye.com \
    --to=tsd@tsdye.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).