Development based workflows

[grantmcdermott]

Hi all. I've really been enjoying this plugin. It's amazing how sluggish everything else feels in comparison.

Having said that, I still haven't landed on a R.nvim workflow that feels great for R package development. To give a sense of what I mean, here's what I'm currently doing whilst working on one of my R packages:

First, I open the directory as per normal with nvim <path/to/mypackage>. However, to open an R.nvim buffer I have to jump down to the R/ folder and open up a random .R file (one that I don't necessarily want to edit), so that I can trigger the local leader rf keymapping. Only once the buffer is open, can I finally run pkgload::load_all() (or similar) to instantiate the package environment for debugging or testing new features.

In contrast, because they are based on workspace logic or project roots, opening up the same package directory in an IDE like Positron or RStudio allows me to immediately run pkgload::load_all() (as well as re-loading in the future; no what file I have open in my editor at the time).

I might be missing something obvious, but is there a way to open up an R.nvim buffer based on a DESCRIPTION file or similar R package (project) anchor? Per the plugin documentation, I don't think so:

R.nvim/doc/R.nvim.txt

Lines 196 to 201 in 7bd12b5

	The plugin is a |file-type| plugin. It will be active only if you are editing
	a .R, .Rnw, .Rd, .Rmd, .qmd or .Rtyp file. The key bindings will not be active
	while editing either unnamed files or files with name extensions other than
	the mentioned above.
	If the plugin is active, pressing <LocalLeader>rf should start R.

:

Should I rather instantiate an external terminal?

Failing that, I'd appreciate any other tips that folks have for (efficient) R package development with this fantastic plugin.

[PMassicotte]

Hi there and thank you for your message, to be sure I understand correctly, you would like to start R.nvim automatically when you open a package directory, iei without having to open a R file first?

[PMassicotte]

Maybe add an option like this?

auto_start = "on project root"

[grantmcdermott]

Hi there and thank you for your message, to be sure I understand correctly, you would like to start R.nvim automatically when you open a package directory, iei without having to open a R file first?

Yes, essentially. Or, to be more precise, at least make the buffer trigger (LocalLeader + rf) available, regardless of whether a specific file type is open in the editor.

Maybe add an option like this?

auto_start = "on project root"

Yeah, that seems reasonable. The specific (and canonical case) that I've described above is an R package. But I can imagine other users would benefit from this setting for R-focused projects, regardless of whether they are packages or not.

[PMassicotte]

Are you loading R.nvim lazily?

[grantmcdermott]

No. Fwiw my config is here: https://github.com/grantmcdermott/dotfiles/blob/main/nvim/.config/nvim/lua/gmcd/plugins/r-nvim.lua

[jasonpott]

Could you adjust your cond statement to recognize the presence of a DESCRIPTION file in the package main directory. Similarly, it could work for .here and .Rproj files at the root level?