[mespe]

I've been using Rmarkdown and knitr for a long while, and have watched its evolution over the years (roughly 8 years now). As someone who does not use RStudio, it's become a bit of a pain for me to use. The authors seem to expect it is being used from RStudio, and using it in a different environment has become a bit fragile.

It's also a bit telling that this "definitive guide" does not include any troubleshooting/debugging sections - the expectation seems to be that it "just works" so long as you use it in RStudio, but otherwise you are on your own.

Not sure that I am aware of many other R packages with this mentality, but I am personally not a fan.

[clircle]

I write my blog mostly in Rmarkdown from Emacs using ESS/polymode. Mostly works well accept for some markdown-mode induced bugginess.

I'm using it occasionally at work as well, but I still prefer R scripts with nice comments for work.

[ska]

I haven't used it for a few years, but I have previously set up some purely command line tooling for this (autogenerated verification reports) which worked well. Is this getting harder to do?

[mespe]

Some functionality has been tied to RStudio's concept of a "project" (https://support.rstudio.com/hc/en-us/articles/200526207-Usin...). I have had several documents authored by others which would not build on my system without some intervention due to this.

[nojito]

You can avoid project related issues by using the here package.

https://github.com/jennybc/here_here

[ska]

Interesting. Thanks.