-
I am relatively new to rocks.nvim and am in the process of transitioning my previous configuration(s) to use rocks. However, I am uncertain about how rocks handles multiple neovim configurations, or if it can at all. It would be beneficial if this were possible. For instance, my default configuration in .config/nvim with init.lua and rocks.toml works perfectly. However, when I switch to .config/nvim-dev, running 'Rocks sync' requires the removal of all plugins from the default rocks.toml file before installing the plugins specified in the new rocks.toml file. Although it is simple to revert, by then using 'Rocks sync' when using the default config, switching between them is inefficient and removing and reinstalling plugins from each respective configuration takes much too long. if I were to be able to separate the installs of the plugins based on the configuration entirely, even if it required duplicates, that would be okay, as I simply want both to have the plugins at their disposal. If there are any suggestions or oversights I'm making, I would really appreciate some help. Thanks ❤️ . |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hey 👋 rocks.nvim uses the standard directories configured by the |
Beta Was this translation helpful? Give feedback.
Hey 👋
rocks.nvim uses the standard directories configured by the
:h NVIM_APPNAME
environment variable.So if you set
NVIM_APPNAME
for your nvim-dev config, rocks.nvim will install plugins into a separate tree than the one for your main config.