lsp_extensions.nvim
lsp_extensions.nvim copied to clipboard
nvim-lua
Repo to hold a bunch of info & extension callbacks for built-in LSP. Use at your own risk :wink:
Clangd-14 also has support for inlay hints (currently needs to be enabled via the `--inlay-hints` flag) via the 'clangd/inlayHints' request. Would be cool if this was supported as well. Probably...
I've just updated both so I'm not 100% sure which one it is (though my money is on RA), but when I start nvim I now get the following error...
`vim.lsp.diagnostic.get` is now being deprecated in favour of `vim.diagnostic.get`. There are more deprecations to be seen in `:h deprecated`.
It is working find but, at them moment it is just normal text, but I would like to colour-code errs as red for example  ``` 1 call plug#begin('~/.vim/plugged') 2...
This allows multiple hints to be displayed on a line, as mentioned in https://github.com/nvim-lua/lsp_extensions.nvim/issues/14#issuecomment-772909849. The current implementation only allows hints of the same kind to appear on a line because...
I don't think it makes much sense to display parameter name hints at the end of the line because 1. they interfere with type hints (I find it confusing to...
I should start by saying I'm very new to neovim and lua, but I'm trying to adopt it as my main editor for Rust dev. The extra rust-analyzer extensions are...
Rust-analyzer has these "extension" commands, which I do not believe are implemented yet with the built-in LSP. Here is an example of one and also the list of them provided...
Neovim version `NVIM v0.5.0-dev+950-g5ce328df4` Loaded the plugin in `~/.local/share/nvim/site/pack/*/start/lsp_extensions.nvim` This is the folder structure ``` . ├── examples │ ├── dart │ │ ├── closing_labels.lua │ │ └── outline.lua │...
