From: tsd@tsdye.com (Thomas S. Dye)
To: William Denton <wtd@pobox.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: No mention of ":results graphics" in docs on code blocks
Date: Sun, 19 Oct 2014 18:44:31 -1000 [thread overview]
Message-ID: <m21tq3wdsg.fsf@tsdye.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1410200000410.21470@shell.miskatonic.org> (William Denton's message of "Mon, 20 Oct 2014 00:07:59 -0400 (EDT)")
Aloha Bill,
William Denton <wtd@pobox.com> writes:
> I just noticed there's no mention of the ":results graphics" header
> argument in the Org manual.
>
> This worg documentation about source code blocks and R does mention it:
>
> http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-R.html
>
> "If the value is :results graphics then 'base' graphics output is
> captured on disk, and a link to the graphics file is inserted into the
> Org Mode buffer (as is also the case with the graphics-only languages
> such as gnuplot, ditaa, dot, and asymptote.)"
>
> (It goes on to say ":results output graphics" is necessary with
> ggplot2 images, but that's no longer true.)
>
> I'm afraid I don't know enough about this header argument or its use
> elsewhere to offer a documentation patch, so I'm just pointing it out.
When I grep "graphics" in the Org mode lisp directory I see that
:results graphics is recognized by ob-core.el, but that the only
language that uses it is R. I think this might be the reason :results
graphics is described with the R documentation and not in the main
manual.
> Working with R code blocks in Org is great.
+1
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2014-10-20 4:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 4:07 No mention of ":results graphics" in docs on code blocks William Denton
2014-10-20 4:44 ` Thomas S. Dye [this message]
2014-10-20 5:00 ` John Hendy
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=m21tq3wdsg.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=wtd@pobox.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).