-
Is there a way I can call the |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
You can take the more manual approach of calling |
Beta Was this translation helpful? Give feedback.
-
I found myself in the same situation and it seems I found nice solution for this. Some background about my setup: I'm using Therefore, I have my primary plugins.lua return require('packer').startup(function()
-- Packer can manage itself
use 'wbthomason/packer.nvim'
...
...
-- Dynamically install other plugins from custom sources.
vim.cmd('runtime! lua/extra-plugins*.lua')
end) And I can have extra plugins installed like this: extra-plugins-corporate.lua local packer = require('packer')
packer.use 'additional-plugin' It took me quite a while to figure out how to dynamically include other plugins to the Packer. Probably it's worth adding to documentation to make it clear. |
Beta Was this translation helpful? Give feedback.
I found myself in the same situation and it seems I found nice solution for this.
Some background about my setup: I'm using
vcsh
andmr
to manage my dotfiles. Any of the tool configuration could have multiple sources: the primary one, which I use everywhere and keep in my public repository and auxiliary one, which is usually referenced to particular environment (e.g. corporate settings) and is stored secretly.Therefore, I have my primary
plugins.lua
with the following content:plugins.lua