|
Hi all, I recently decided to give neovim a go, and have been enjoying myself learning about it. NVChad caught my eye early on, but I decided to try and piece together my own config as a learning experience. After getting everything I wanted working (including a Roslyn lsp for Unity game dev), I decided to just use NVChad as a base, mainly because I couldn't be bothered trying to make my own config look nice :D Anyway, I've been customising various aspects to my liking, but something I haven't been able to figure out is how to customise nvimtree. Reading through the docs, it looks like I should be able to add override config in I saw a random post on Reddit suggesting you can add cutom/override lua files to override config, but I also haven't been able to find any docs on this? Thanks in advance! |
Replies: 2 comments
|
no this is wrong nvimtreee is a plugin, so make a table for it in your plugins file https://nvchad.com/docs/config/plugins chadrc is just copy of this one https://github.com/NvChad/ui/blob/v3.0/lua/nvconfig.lua lazy will merge plugin tables as per order, like{
"abc/xyz",
cmd = "Hi",
opts = { width = 10 }
}
{
"abc/xyz",
event = "VeryLazy",
opts = { width = 20, icons = true }
}Now whats the final table? its this {
"abc/xyz",
cmd = "Hi",
event = "VeryLazy",
opts = { width = 20, icons = true}
}Now you might ask which sane user would define same plugins like that? 😂 , none does that, but distros will do! So in this example u can see nvchad's main repo is installed as a plugin and that repo has only 1 module, which is So nvchad.plugins module has list of our default plugins , and the user has module Now by this we can conclude that first Default plugins of NvChad and then the user plugins are initialized, lazy merges them properly! |
|
Many thanks @siduck, it's all starting to make sense... |
no this is wrong
nvimtreee is a plugin, so make a table for it in your plugins file
https://nvchad.com/docs/config/plugins
chadrc is just copy of this one https://github.com/NvChad/ui/blob/v3.0/lua/nvconfig.lua
lazy will merge plugin tables as per order, like
{ "abc/xyz", cmd = "Hi", opts = { width = 10 } } { "abc/xyz", event = "VeryLazy", opts = { width = 20, icons = true } }Now whats the final table? its this
{ "abc/xyz", cmd = "Hi", event = "VeryLazy", opts = { width = 20, icons = true} }Now you might ask which sane user would define same plugins like that? 😂 , none does that, but distros will do!
So in this…