RMarkdown

[memeplex]

Consider adding support for rmarkdown+knitr that is currently just pandoc-markdown with embedded R, preprocessed by knitr to generate pure pandoc-markdown. I think vim-pandoc has all the elements there to implement this in a more or less straightforward way. RMarkdown is a very important tool for the R community but proper tool support is currently confined to RStudio. Despite this, a lot of people uses R outside an IDE and could find a vim-based alternative very attractive.

[memeplex]

I could help with this task, at least providing the R bits.

[fmoralesc]

👍
I think we should make this a separate plugin (like vim-criticmarkup), however, because it seems a bit niche, reusing vim-pandoc and vim-pandoc-syntax as needed, of course. I can create a repo under vim-pandoc and add you as collaborator so we can organize things better. What do you think?

[memeplex]

Sure, but you will have to help me with some scaffolding and code
organization, I'm pretty fluent at vimscript but vim-pandoc is a big plugin
and I would like to use it in a consistent way.

Btw, it's not as niche as you may believe. Reproducible research is kinda
hyped buzzword currently. R is a niche language but for an important niche.
And pythonists doing stats would benefit from this too, as knitr is
polyglot.

On Sat, Jul 12, 2014 at 1:53 PM, Felipe Morales notifications@github.com
wrote:

[image: 👍]
I think we should make this a separate plugin (like vim-criticmarkup
https://github.com/vim-pandoc/vim-criticmarkup), however, because it
seems a bit niche, reusing vim-pandoc and vim-pandoc-syntax as needed, of
course. I can create a repo under vim-pandoc and add you as collaborator so
we can organize things better. What do you think?

—
Reply to this email directly or view it on GitHub
#56 (comment)
.

[memeplex]

Mainly what you need is to activate syntax highlight for R code blocks as a
default and to set an R snippet calling knitr instead of plain pandoc as a
"builder". knitr uses rmarkdown which is just built on top of pandoc.

On Sat, Jul 12, 2014 at 1:57 PM, Carlos Pita carlosjosepita@gmail.com
wrote:

Sure, but you will have to help me with some scaffolding and code
organization, I'm pretty fluent at vimscript but vim-pandoc is a big plugin
and I would like to use it in a consistent way.

Btw, is not as niche as you may believe. Reproducible research is kinda
hyped buzzword currently. R is a niche language but for an important niche.
And pythonists doing stats would benefit from this too, as knitr is
polyglot.

On Sat, Jul 12, 2014 at 1:53 PM, Felipe Morales notifications@github.com
wrote:

[image: 👍]
I think we should make this a separate plugin (like vim-criticmarkup
https://github.com/vim-pandoc/vim-criticmarkup), however, because it
seems a bit niche, reusing vim-pandoc and vim-pandoc-syntax as needed, of
course. I can create a repo under vim-pandoc and add you as collaborator so
we can organize things better. What do you think?

—
Reply to this email directly or view it on GitHub
#56 (comment)
.

[fmoralesc]

I didn't mean to say it was niche in a bad way, simply that the number of general markdown users > rmarkdown users. As you said, vim-pandoc is pretty big already, and we have separate repos for third party vim plugins integration and syntax files.

I'll need more specifics on how the execution pipeline should work, I've never used R myself (currently looking into it).

Anyway, I'll go ahead and create vim-rmarkdown as a repo for the vim-pandoc org, and add you as a contributor. Will close this and open a new discussion over there, for figuring out details.

[fmoralesc]

vim-pandoc/vim-rmarkdown#1