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:
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:Before you provide your plugins within paq, you need to call the setup function and provide the path there, following your folder convention:
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.