-
The plugins come from the "Lazyvim" files in the plugins folder. I don't remember the exact path for linux but it should be somewhere in the data folder. All the plugins' config is stored there (same ones in the link).
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
Figuring out what should be added is... an art (e.g. mason expects "bash-language-server", treesitter "bash", lspconfig "bashls"). The official docs with the official naming can be helpful here (nvim-lspconfig , treesitter , mason )
-
mason.nvim
Portable package manager for Neovim that runs everywhere Neovim runs. Easily install and manage LSP servers, DAP servers, linters, and formatters.
Figuring out what should be added is... an art (e.g. mason expects "bash-language-server", treesitter "bash", lspconfig "bashls"). The official docs with the official naming can be helpful here (nvim-lspconfig , treesitter , mason )
-
Separately - big kudos to lucazz whose dotfiles I have been looking at, in search for understanding :)
-
in my dotfiles, I have a default function that runs lspconfig for every language server, except for rust-analyzer where it invokes rust-tools which will run lspconfig for me with some extra features.