DEV Community

loading...

Discussion on: Installing neovim nightly alongside stable

Collapse
creativenull profile image
Arnold Chand Author

Hey!

This is nice! But a bit overly complicated, and I guess that's one of the limitations of keeping separately namespaced nvim configs that would lead to doing the hacky way you provided. Don't get me wrong that's a nice implementation 🙂

Although here is something you can try with paq-nvim if you have the time. I've checked through paq-nvim docs and, while a bit obscure, there is a way to change where to install the plugins, and that is thru the setup() function.

Make sure you git clone paq-nvim to the correct directory that was set in your packpaths, following your folder convention:

git clone --depth=1 https://github.com/savq/paq-nvim.git \
    "${XDG_DATA_HOME:-$HOME/.local/share}"/nvim-lua/site/pack/paqs/start/paq-nvim
Enter fullscreen mode Exit fullscreen mode

Before you provide your plugins within paq, you need to call the setup function and provide the path there, following your folder convention:

local paq = require 'paq-nvim'

paq.setup {
  path = vim.env.HOME .. '/.local/share/nvim-lua/site/pack/paqs/'
}

paq {
  'savq/paq-nvim';

  -- your plugins below
}
Enter fullscreen mode Exit fullscreen mode

I have not tried this myself so do let me know if this helps out or not with keeping your configs separate with different directories.