emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tsd@tsdye.com (Thomas S. Dye)
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
	Eric Schulte <schulte.eric@gmail.com>
Subject: Re: org-babel header documentation
Date: Tue, 26 Mar 2013 06:54:51 -1000	[thread overview]
Message-ID: <m1sj3iw17o.fsf@tsdye.com> (raw)
In-Reply-To: <CA+M2ft-Kg+ffdtDsSUAzEWpSMzHfL4h_PObai_8M+-Dh=vmRdg@mail.gmail.com> (John Hendy's message of "Tue, 26 Mar 2013 11:23:45 -0500")

Aloha all,

John Hendy <jw.hendy@gmail.com> writes:
>> Hi Eric,
>>
>> thanks a lot BTW for all you've done.
>>
>> What about to have a list editable for all interested
>> w/ comments to all header args in alphabetical order?
>>
>> Might participate and write it down the way it's understood.
>> You and others may correct it on the fly.
>>
>> Maybe someone starts a headers.org in Worg?
>
> I'm happy to help with this. Will take me a bit to get to (~1wk), but
> could definitely help. I'm really trying to help more with Worg as my
> return for all the code and support others write. One problem with
> this, though, is that some of these are language specific. I ran into
> this before:
> - http://lists.gnu.org/archive/html/emacs-orgmode/2012-07/msg00260.html
>
> So... this table might be more complicated than you realize, unless
> you're only talking about system-wide arguments.
>

Another way to approach this would be two-pronged: 1) patch the Org manual
where appropriate, and 2) augment (or draft) the language-specific guides on
Worg. Most of the language guides are stubs waiting for detailed content
from users.  There are still many languages without a guide (see
http://orgmode.org/worg/org-contrib/babel/languages.html).  The template
for language guides
(http://orgmode.org/w/?p=worg.git;a=blob;f=org-contrib/babel/languages/ob-doc-template.org;hb=HEAD)
has a section for header arguments, so there is a structure in place.

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

  reply	other threads:[~2013-03-26 16:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 15:00 org-babel header documentation Andreas Röhler
2013-03-26 15:23 ` John Hendy
2013-03-26 15:35   ` Eric Schulte
2013-03-26 16:17     ` Andreas Röhler
2013-03-26 16:23       ` John Hendy
2013-03-26 16:54         ` Thomas S. Dye [this message]
2013-03-26 16:33       ` Eric Schulte
2013-03-29 17:58         ` Eric Schulte
2013-03-29 20:54           ` John Hendy
2013-03-29 21:13             ` Eric Schulte
2013-03-30  1:54               ` Eric Abrahamsen
2013-03-30 15:17                 ` Eric Schulte
2013-03-30 22:13                   ` Charles Berry
2013-03-31  0:49                     ` Eric Abrahamsen
     [not found]                   ` <87mwtkapcq.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-04-10 20:39                     ` Sebastien Vauban

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=m1sj3iw17o.fsf@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jw.hendy@gmail.com \
    --cc=schulte.eric@gmail.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).