Why vim.g.*
options doesn't work in a custom plugin config?
#861
Replies: 2 comments 12 replies
-
vim.g doesn't work in init.lua for me :/ |
Beta Was this translation helpful? Give feedback.
-
@ahhshm @johnsiras @siduck I believe this is a nvim-tree issue but there is some really strange stuff going on here. It seems that the vim globals must be set before nvim-tree is required (Even the ones in the NvChad nvimtree default config appear to be having 0 effect because of this). I believe they are moving config options to lua instead of vim globals so eventually this will be fixed, but in the mean time I found a solution. Edit: @siduck this is not really an issue on our end but since the globals in our config are doing nothing right now, lmk if you want me to clean this up a bit and pr it, but take a look at terminals first lol :) Place this in your init.lua or wherever your custom plugin table is:
Place this in custom.plugins.overrides.nvimtree (or change the paths above and put it elsewhere) and make whatever changes you like
|
Beta Was this translation helpful? Give feedback.
-
Hi
nvim-tree
has some options that I want to override and i can't do this in the setup function. like this one:I've put my custom configs in "custom.plugins.configs.nvimtree":
The
vim.g.*
options don't seem to work. but when I put them incustom/init.lua
they work. Why?When I pass a path to
default_plugin_config_replace
the original configs shouldn't be loaded, right?Beta Was this translation helpful? Give feedback.
All reactions