From: John Hendy <jw.hendy@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-babel header documentation
Date: Fri, 29 Mar 2013 15:54:25 -0500 [thread overview]
Message-ID: <CA+M2ft--SOrMK11KWj7p0TGr0rZXvy9TS3n-edvQfi5VnZhatQ@mail.gmail.com> (raw)
In-Reply-To: <87hajuqe9a.fsf@gmail.com>
On Fri, Mar 29, 2013 at 12:58 PM, Eric Schulte <schulte.eric@gmail.com> wrote:
> Eric Schulte <schulte.eric@gmail.com> writes:
>
>> Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
>>
>>> Am 26.03.2013 16:35, schrieb Eric Schulte:
>>>> John Hendy <jw.hendy@gmail.com> writes:
>>>>
>>>>> On Tue, Mar 26, 2013 at 10:00 AM, Andreas Röhler
>>>>> <andreas.roehler@easy-emacs.de> wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> while digging through the org-babel stuff, which is quite exiting, have some
>>>>>> difficulties to grasp the functionality of different header arguments.
>>>>>>
>>>>>> Info 14.8 Header arguments
>>>>>>
>>>>>> is useful so far. Still miss an explanation the way
>>>>>>
>>>>>> Setting X to Y will cause....
>>>>>>
>>>>>> Maybe missing the right spot still?
>>>>>
>>>>> I tend to agree. I typically just follow the matching tutorial for
>>>>> whatever language I'm using and stick to it... but I don't always
>>>>> understand (like why I need =:results output graphics= in R vs. just
>>>>> output). Perhaps you could inquire about a particular header setting,
>>>>> someone could respond, and you could add the info to Worg somewhere
>>>>> (something like a "layman's guide to header arguments")?
>>>>>
>>>>
>>>> The evolution of the code block functionality over the years has been
>>>> driven almost exclusively by this mailing list. The best way to find
>>>> the reasoning behind any particular baroque combination of header
>>>> arguments is to search through the archives of this list.
>>>>
>>>> Sadly we don't do a good enough job of ensuring that the content
>>>> generated here makes its way to Worg. I'm certainly guilty of this
>>>> myself, but there are only so many hours in the day.
>>>>
>>>
>>> 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?
>>>
>>> Andreas
>>>
>>
>> I like that idea a lot. Please start such a page, and link to it from
>> one of the main Babel pages.
>>
>
> In fact such a page already exists. I've just added the solution for
> how to set language and file local default header argument values there.
> If you can think of anything else of use that came from this discussion
> please feel free to add them to that page.
>
Exists on Worg? Sorry for my obtuseness, but I'm not finding it.
John
> --
> Eric Schulte
> http://cs.unm.edu/~eschulte
next prev parent reply other threads:[~2013-03-29 20:54 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
2013-03-26 16:33 ` Eric Schulte
2013-03-29 17:58 ` Eric Schulte
2013-03-29 20:54 ` John Hendy [this message]
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=CA+M2ft--SOrMK11KWj7p0TGr0rZXvy9TS3n-edvQfi5VnZhatQ@mail.gmail.com \
--to=jw.hendy@gmail.com \
--cc=emacs-orgmode@gnu.org \
--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).