vim-lsp
vim-lsp copied to clipboard
async language server protocol plugin for vim and neovim
Hi, Is there a supported way to pass a specific range when formatting (`'[` -> `']` for using with InsertLeave / TestYankPost for example ?) Reading https://github.com/prabirshrestha/vim-lsp/blob/master/plugin/lsp.vim#L134-L135 and https://github.com/prabirshrestha/vim-lsp/blob/master/autoload/lsp/internal/document_range_formatting.vim#L105-L111 makes...
https://github.com/prabirshrestha/vim-lsp/blob/14f9ab319ff96eea16ef6dbf57ed801c8fc8967e/autoload/vital/_lsp/VS/Vim/Buffer.vim#L54 The above line adds a named buffer. Since [only unnamed buffers are skipped by viminfo](https://github.com/prabirshrestha/vim-lsp/issues/1337) vim-lsp leaves file-marks in `viminfo` when enabled. This seems unnecessary for a temporary buffer,...
Hello, I am experiencing an error when I run the `:LspSignatureHelp` command. When I hover over a function and run that command, I get this. Notice no syntax highlighting: ![image](https://user-images.githubusercontent.com/19850526/179079285-3d704e0d-bba0-4eca-b280-4323dc372338.png)...
I recently re-installed metals via the `vim-lsp-settings` plugin, and looks like it's now pulling down v0.11.7 released a week ago. The initialization step fails with: ```json { "response": { "id":...
I have a wsl2 file system mounted on a network drive with smb and using clangd in Windows 10. (Z: is mounted to \\ubuntu2204\username) When I use LspDefinition with a...
I am using clangd as a C LSP server in vim-lsp. The SignatureHelp popup highlights '_' as markdownError as shown in the image below, which looks bad. ![signaturehelp](https://user-images.githubusercontent.com/12369962/167223843-4aa138ca-7360-4dfb-be0e-763d8b2bf491.png) I am...
When displaying a popup window with LspPeekDefinition, etc., garbled characters occur if the encoding of the file is different from the vim's internal encoding. I have confirmed that by converting...
Hi. Thanks for your great developing. No vim-lsp, no my Vim life. I have an issue that [floating window borders are always rendered with ASCII characters if `ambiwidth` option is...
After c075e157fcce4511e537b1f7f3385444d9c80e0d, Floating window will be hidden sometimes unintentionally with `rls` when `g:lsp_diagnostics_float_cursor` is enabled.
I can see `codeLens/resolve` is supported, but how about `codeAction/resolve`? Any plan ahead? https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#codeAction_resolve