Justin M. Keyes
Justin M. Keyes
> Use the latest stable in the documentation instead of nightly. Not in favor. The website docs allow us to make hints and other docs available via the website search...
> The version-specific docs could live at e.g. `https://neovim.io/doc/user/v0.10/`. Instead of this, let's double-down on the `@since` annotations, at least to start with. And we can make those more prominent...
> But that won't work with current "soft deprecations" which _hide_ the documentation They will be on deprecated.txt ?
Surely this is a bug in the kotlin server? What is needed from nvim-lspconfig, which is just a collection of data?
first 2 lines: > [Configs](https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md) for the [Nvim LSP client](https://neovim.io/doc/user/lsp.html) (:help lsp). however, it could be clearer. and needs some explanation.
> I'm not sure why we can't rely purely on the root_dir from the client and remove this test ? SGTM. The LspInfo code lives here: https://github.com/neovim/nvim-lspconfig/blob/master/lua/lspconfig/health.lua , PR welcome
No longer relevant since we migrated to `vim.lsp.config` The healthcheck now lives in Nvim core: :che vim.lsp If there's a bug in it, report it to Nvim core.
Well reasoned. Thank you
No idea about mason. Wherever you set "tsserver", change that to "ts_ls".
Why not just change the "tsserver" item in `ensure_installed` to "ts_ls" ?