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
If you find your LSPs do not start or an error is thrown when using the home manager template's example configuration, either your nixpkgs channel provided to your neovim is too old and doesnt have nvim-lspconfig 2.0.0 or nvim 0.11, or you pulled the template before it has been updated to use the new lsp configuration scheme.
You can pass a new nixpkgs to use via the nixpkgs_version module option
If you cannot update your nixpkgs input for other reasons, you should ensure you are using nvim 0.11+ still, (latest stable nixpkgs release, or set neovim-unwrapped setting in packageDefinitions) and then pull the newest version of nvim-lspconfig
If your dependencyOverlays list or addOverlays option contains a call to the standard plugin overlay, you may then replace pkgs.vimPlugins.nvim-lspconfig with pkgs.neovimPlugins.nvim-lspconfig
If it doesn't, you can replace it with (mkPlugin "nvim-lspconfig" inputs.plugins-nvim-lspconfig) instead. (Where mkPlugin is provided by the arguments to your categoryDefinitions)
The text was updated successfully, but these errors were encountered:
If you find your LSPs do not start or an error is thrown when using the home manager template's example configuration, either your nixpkgs channel provided to your neovim is too old and doesnt have nvim-lspconfig 2.0.0 or nvim 0.11, or you pulled the template before it has been updated to use the new lsp configuration scheme.
You can pass a new nixpkgs to use via the nixpkgs_version module option
Neovim recently updated the way it does its lsps.
If you cannot update your nixpkgs input for other reasons, you should ensure you are using nvim 0.11+ still, (latest stable nixpkgs release, or set neovim-unwrapped setting in packageDefinitions) and then pull the newest version of
nvim-lspconfig
If your dependencyOverlays list or addOverlays option contains a call to the standard plugin overlay, you may then replace
pkgs.vimPlugins.nvim-lspconfig
withpkgs.neovimPlugins.nvim-lspconfig
If it doesn't, you can replace it with
(mkPlugin "nvim-lspconfig" inputs.plugins-nvim-lspconfig)
instead. (WheremkPlugin
is provided by the arguments to your categoryDefinitions)The text was updated successfully, but these errors were encountered: