Lua filetype detection is enabled by default in neovim nightly so we don't need those two options. The reason we can't simply override them in `custom/init.lua` is that setting `did_load_filetypes` to any value, completely disables filetype detection (and therefore syntax highlighting) and this may confuse people that use neovim nightly. I know NvChad doesn't officially support neovim nightly but people may want to try it to see the new features and this PR makes their life easier. Also, you do a similar check in `plugins/configs/lspconfig.lua` so I thought it's ok :)
before we were using variables/fields to setup custom lspconfig but today I realized that we dont even need that, we can just modify default lspconfigs config
remove vim tsparser as it is adviced to have 100% lua config and vim.cmd adds a lil overhead as compared to native vim api functions, increase shiftwidth as it looks better
• problem: providers are incorrectly disabled
• why: providers must be disabled by
setting their global value to 0,
unlike default plugins.
• solution: disable built-in providers by
setting their values to 0
instead of 1
As this causes issues (buf switching i.e tbufbnext/tbufprev) not working properly when nvim is opened with multiple files dbb3439982 (commitcomment-77092312)
In order to ensure that plugin configuration that is overridden with a
function instead of a table is still merged with the default plugin
configuration, this commit splits up the if/elseif/else statement in
lua/core/utils.lua.
This is necessary as we want to take the resulting table returned from
the override function and merge it with the default_table before setting
up the plugin.
Fixes [this issue](https://github.com/NvChad/NvChad/issues/1239)
added cmd fields for various plugins for example lspinstaller+lspconfig gets loaded only when a file opened but their commands can be run before a file is opened so I additionally lazy loaded them on their cmds too
removed nvim-gps as nvim-navic or winbar.nvim will be added when v0.8 neovim releases. Removed lsp signature as I was able to emulate showing args with the default signature help() window
