beps, to neovim

By using Nvim-R instead of RStudio for my R packages maintenance I have the feeling of gaining a deeper control of the process. I understand all the steps better. Even for building a documentation website with devtools, roxygen2 and pkgdown.
I won't drop RStudio though. It’s nice to be free to choose one tool or the other.

devSJR,
@devSJR@fosstodon.org avatar

@beps I truly understand what you mean. I am now talking a little about . We have a solid integration of , and some other tools. works. A tight integration of would be nice. We have a good R console and a terminal. Likewise, we don't have the deep integration of , and . Some find it good (I) others find it a hindrance.
In the end, there are many good choices.

smach, to rstats
@smach@masto.machlis.com avatar

The {document} 📦 creates roxygen2-style documentation for functions that aren't (yet) part of an R package.

In the screenshot below, top left shows a test.R file with a function called test_function , including roxygen definitions. After running

d <- document("test.R")

I can use

?test_function

to read the help file as if it were part of a package.

By Andreas Dominik Cullmann

https://cran.r-project.org/web/packages/document/vignettes/Introduction_to_document.html

@rstats

  • All
  • Subscribed
  • Moderated
  • Favorites
  • megavids
  • thenastyranch
  • magazineikmin
  • osvaldo12
  • GTA5RPClips
  • mdbf
  • Youngstown
  • tacticalgear
  • slotface
  • rosin
  • kavyap
  • ethstaker
  • everett
  • khanakhh
  • JUstTest
  • DreamBathrooms
  • InstantRegret
  • cubers
  • normalnudes
  • Leos
  • ngwrru68w68
  • cisconetworking
  • modclub
  • Durango
  • provamag3
  • anitta
  • tester
  • lostlight
  • All magazines