From: "Thomas S. Dye" <tsd@tsdye.com>
To: "Charles C. Berry" <ccberry@ucsd.edu>
Cc: org mode <emacs-orgmode@gnu.org>
Subject: Re: Babel R source blocks problem
Date: Fri, 10 Feb 2017 19:29:42 -1000 [thread overview]
Message-ID: <m2h9412t2x.fsf@tsdye.com> (raw)
In-Reply-To: <alpine.OSX.2.20.1701281343390.2194@charles-berrys-macbook.local>
Aloha Chuck,
Charles C. Berry writes:
>
> A look at the `slidify-example.org' file in the `org-9-plus' branch of my
> (chasberry) `orgmode-accessories' github repo might be a good start with
> .Rmd exports even if you do not want to use `slidify'.
Your ox-ravel exporter is a pleasure to use. I'm farther along than I
thought I'd be at this point.
I'm new to much of the R ecosystem, including slidify, so forgive some
noob ignorance in the following three questions:
1) I've specified the properties EXPORT_TITLE and EXPORT_AUTHOR, but
they don't show up in the .Rmd file. Is this a limitation of ox-ravel,
or do I need to learn how to insert them in the Org mode source?
2) How do I instruct ox-ravel to include the graphics output of a source
code block? I tried :ravel fig=TRUE as a header to the source code
block, but no dice. Most of my experience is with ox-latex, so that
colors my expectations here; i.e. I'm expecting a [[file:myfile.pdf]]
link to produce a graphic in the output.
3) I've been knitting the .Rmd output using RStudio, which is also new
to me. I don't mind doing this (it is what the session organizer is
going to do with the .Rmd file I send next week), but I'm wondering
if you have an emacs-only solution?
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2017-02-11 5:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-28 19:29 Babel R source blocks problem Thomas S. Dye
2017-01-28 20:25 ` Charles C. Berry
2017-01-28 21:31 ` Thomas S. Dye
2017-01-28 22:18 ` Charles C. Berry
2017-01-29 0:21 ` Thomas S. Dye
2017-02-11 5:29 ` Thomas S. Dye [this message]
2017-02-11 20:02 ` Charles C. Berry
2017-03-13 22:37 ` Thomas S. Dye
2017-03-20 18:19 ` Charles C. Berry
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=m2h9412t2x.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
/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).