You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This very well could be considered a feature request but I thought to ask here first.
I'm curious regarding multiple plugins in the same use statement,
if this is not currently supported are there any plans to accept this kind of configuration?
Or if it is supported, can someone verify why it's not working as expected.
I noticed this being recommended by the nvim-lsp-installer plugin and was testing it out
use {
'neovim/nvim-lspconfig',
'williamboman/nvim-lsp-installer',
-- config = function() require('lsp').config()
}
Attempting to add an anonymous config to this doesn't seem to get executed.
I placed a nvim_echo at the top of the module as a sort of sanity check and it never ran.
So, to me It appears as if packer is able to recognize the plugins and doesn't give any issues when compiling or installing,
but doing so makes the config function not work properly.
Note: I didn't test other variables like requires or after
Additional Context: Colorscheme / Highlights
With regards to this: Another use case I was aiming for was to have my color schemes loaded by the same use block.
This could potentially allow some settings to be initialize for only the active theme without multiple calls to my custom setup.
use {
'mofiqul/vscode.nvim',
'folke/tokyonight.nvim',
'numtostr/sakura.nvim',
'morhetz/gruvbox',
config=function()
-- colors_name defined in main init.luarequire('colors').setup(vim.g.colors_name)
end
}
As opposed to something like this,
where I supply the theme name to check against the current colors_name and return if they don't match.
use {
'numtostr/sakura.nvim',
config=function() require('colors').setup('sakura') end
}
use {
'morhetz/gruvbox',
config=function() require('colors').setup('gruvbox') end
}
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
This very well could be considered a feature request but I thought to ask here first.
I'm curious regarding multiple plugins in the same
use
statement,if this is not currently supported are there any plans to accept this kind of configuration?
Or if it is supported, can someone verify why it's not working as expected.
I noticed this being recommended by the nvim-lsp-installer plugin and was testing it out
Attempting to add an anonymous
config
to this doesn't seem to get executed.I placed a
nvim_echo
at the top of the module as a sort of sanity check and it never ran.So, to me It appears as if packer is able to recognize the plugins and doesn't give any issues when compiling or installing,
but doing so makes the
config
function not work properly.Note: I didn't test other variables like
requires
orafter
Additional Context: Colorscheme / Highlights
With regards to this: Another use case I was aiming for was to have my color schemes loaded by the same
use
block.This could potentially allow some settings to be initialize for only the active theme without multiple calls to my custom setup.
As opposed to something like this,
where I supply the theme name to check against the current
colors_name
and return if they don't match.Beta Was this translation helpful? Give feedback.
All reactions