Re: Anyone using or interested in an org to Rmarkdown exporter?

["Charles C. Berry" <ccberry@ucsd.edu>]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1551 bytes --]

On Sat, 1 Nov 2014, Rasmus wrote:

> Hello,
>
> Grant Rettke <gcr@wisdomandwonder.com> writes:
>
>> • Does one exist and I missed it?
>
> Are you aware of this project?
>
>    https://github.com/chasberry/orgmode-accessories
>
> —Rasmus


Thanks for this, Rasmus.

Grant,

If ox-ravel is something you are interested, I recommend that you
tryout the `ravel-lang' branch. In addition to the examples in the
master branch, there is `demos.org' with some simple examples.

As to Thorsten's query:

,----
| what would acutally be the benefit of using RMarkdown over Org-mode,
| or put it another way - when you already use RMarkdown, why do you
| need Org-mode too? And if you use Org-mode, what does RMarkdown add to
| the table?
`----

There is some discussion of this in the README.org...

If you already use org-mode:

You get access to Sweave, knitr, slidify, pander, et cetera.

Their `chunk' options (akin to babel header args) can be easier to use
than header args for complicated displays.

Dependency aware caching of R objects is available in those engines and 
its lack in Babel [1] is a serious impediment to working with long running 
computations.

bioConductor vignettes can be authored in org-mode and exported for a
suitable vignette engine.

If you already use Rmarkdown, etc, you get the ease of editting and
working in org-mode - cycling visibility of headlines, lists, src
blocks, and results, and of storing results inline, previewing latex
fragments, and all.

HTH,

Chuck

[1] Yes, I do know that there is a :cache header arg.