From: tsd@tsdye.com (Thomas S. Dye)
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Manual does not list :results output graphics as babel header arg
Date: Tue, 10 Jul 2012 05:19:25 -1000 [thread overview]
Message-ID: <m1sjczk5j6.fsf@tsdye.com> (raw)
In-Reply-To: <CA+M2ft9DdknMEHwBLDm9_H0kOuv+dusUeajnDy9ikfG3M-oZdQ@mail.gmail.com> (John Hendy's message of "Mon, 9 Jul 2012 23:13:11 -0500")
John Hendy <jw.hendy@gmail.com> writes:
> On Mon, Jul 9, 2012 at 7:35 PM, Thomas S. Dye <tsd@tsdye.com> wrote:
>> John Hendy <jw.hendy@gmail.com> writes:
>>
>>> I have typically outputted graphics from R via tikzDevice manually,
>>> but gave my first whirl to just including things via the :file
>>> argument in my block header. In the process, I was trying to get this
>>> to work and found I needed to use:
>>>
>>> -----
>>> :results output graphics
>>> -----
>>>
>>> This is listed on Worg ob-R-doc:
>>> - http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-R.html#sec-4-3
>>>
>>> But I didn't originally know about it, as it's not a listed header
>>> argument in the manual, which is where I check since they're all
>>> listed in one place:
>>> - http://orgmode.org/manual/results.html#results
>>>
>>> Does the manual only list universal babel header arguments and R is in
>>> a subset of ones using =:results output graphics= or should it be
>>> there?
>>>
>>
>> Hi John,
>>
>> The babel header arguments are implemented at two levels.
>>
>> There are general babel arguments that apply to all the supported
>> languages. These are described in the manual.
>>
>> It is also possible for the individual language implementations to
>> define their own header arguments. R is a good example, where the very
>> many arguments to the various R output devices are built into ob-R.el.
>> These language specific header arguments are not described in the
>> manual, but instead appear in the language specific documentation on
>> Worg.
>>
>> Re: your specific question about :results output graphics. I believe
>> this is an R specific header argument and that it is described in the
>> appropriate place in the documentation on Worg (see lines 68 and 230
>> of ob-R.el).
>>
>> The manual is not a one-stop source for answers to all Babel questions.
>> Recourse to the language specific documentation is typically necessary,
>> which is why it would be great if someone could find time to work up
>> documentation for the 20 or so languages that still lack it :)
>
> Thanks for the clarification and that answers the question. This was a
> specific header argument for R. Perhaps the manual could link to this
> page?
> - http://orgmode.org/worg/org-contrib/babel/languages.html
>
> Maybe with a diddy: "Some languages feature their own unique header
> arguments. The above document only universal, system wide Babel header
> arguments and one should consult the specific language page on Worg
> for additional features."
>
> Just a thought.
Hi John,
Thanks for this thought, which is indeed reasonable. I thought the
manual might lack this structure, but when I went back to the
manual I found that
http://orgmode.org/manual/Specific-header-arguments.html#Specific-header-arguments
has this at the bottom of the page: "Additional header arguments are
defined on a language-specific basis, see Languages", where "Languages"
is a link to another manual page, one with a table of supported
languages and a link to the Worg page you cite.
The language is a bit different than your proposal, but the path seems
clear enough to me.
Of course, there is still the issue of the languages that lack
language-specific documentation :)
All the best,
Tom
--
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com
next prev parent reply other threads:[~2012-07-10 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 21:08 Manual does not list :results output graphics as babel header arg John Hendy
2012-07-10 0:35 ` Thomas S. Dye
2012-07-10 4:13 ` John Hendy
2012-07-10 15:19 ` Thomas S. Dye [this message]
2012-07-10 16:03 ` John Hendy
2012-07-10 17:17 ` [PATCH] " Thomas S. Dye
2012-07-10 19:34 ` [Accepted] " Bastien Guerry
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=m1sjczk5j6.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=jw.hendy@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).