Easiest/most automated way to get tags working for all R packages installed outside of base R and current package projects?

[CJ M]

The documentation in the section for *Nvim-R-tagsfile* focuses on base R code, but doesn't how to do this at scale for all your packages you get from CRAN and elsewhere, etc.

Is there an easy way to get tags working for all installed packages (From CRAN and elsewhere) outside of the current package you are already working on?

Just to clarify, I can already get the tags generated quickly and easily for the existing package being developed via RBuildPackageTags using the vim-devtools-plugin.

This is one nice thing that Rstudio offers out of the box when you're developing a new package ... you can "F2"/jump into any (exported) function definition from another package, and generally you can see source code on the spot.  I want to replicate this behaviour with many packages in Nvim-R.

Right now I'm downloading the packages (With source code) on a case by case basis, opening a temporary, *.R file within the package folder, starting R, and call RBuildPackageTags from the command line mode.  And repeating this on a case by case basis as I want to see the source of functions in other packages. ANd slowly ~/.rtags builds up over time.

This process is kind of clunky, and I could look at writing scripts to do it for many packages, but I'm wondering if something to do this already exists, or I've overlooked something?

[Jakson Alves de Aquino]

Unfortunately, Nvim-R doesn't have any features to make this task easier. I don't need this feature, but I could merge a pull request for this if someone wrote one.