dotfiles
vim-lsp
| dotfiles | vim-lsp | |
|---|---|---|
| 1 | 81 | |
| 0 | 3,017 | |
| - | - | |
| 0.0 | 6.4 | |
| over 3 years ago | 7 days ago | |
| Vim Script | Vim Script | |
| - | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dotfiles
-
Anybody here use Neovim as their editor? Would you recommend anything over Neovim?
I have a basic setup you can see if you’d like, although I’m not so sure how up to date it is: https://github.com/jakereps/dotfiles
vim-lsp
-
Using SonarLint language server in Vim?
Has anybody managed or got an idea how to make SonarLint Language Server work with e.g. vim-lsp?
-
Vim Golang syntax is ugly
You need to configure a language server. For C++ it's a bit tricky, so good luck with Go. There are other plugins that provide semantic highlighting using LSP, for example https://github.com/prabirshrestha/vim-lsp (I didn't try it, but it seems good).
-
Vim-writegood: nothing, but a simple Vim9 wrapper around write-good.
ALE can use LSP as well. And if you are using vim-lsp, you can use the same instance of server for both with vim-lsp-ale bridge plugin.
-
small vimrc and lsp?
I feel the same way. Not a one-liner but the smallest config LSP plugin I've found is vim-lsp. It works in both Vim and Neovim.
-
Should I move to NeoVim?
The only major feature that Neovim still has is a built in LSP client. But I find the built in Neovim LSP client is unusably buggy, you're much better off using any of the other LSP plugins. What I use is vim-lsp, but I've tried all of the major lsp client, they are all significantly better than the built in Neovim LSP.
- Starting with linux, my experience
- Does vim have a built in/plugin version of vscode's command click?
-
install lsp in vim
As for install/configuration, all you need is the latest Vim, the plugins I mentioned, and that bit in your vimrc. You can do a bit better than that if you copy the entire config with mappings from the vim-lsp GitHub page.
-
How to improve deoplete and vim-lsp (pylsp /jedi-language-server)
I have a problem with Deoplete and Vim-LSP completion (Python's Pylsp and Jedi-Language-Server). The suggestion is much less, and it also misses a lot of opportunities to suggest compared to Deoplete-Jedi, which literally defeats the former by a large margin. Is there a setting to make this duo works like deoplete with deoplete-jedi?
-
The Ruff python linter is insanely good
- add the [prabirshrestha/vim-lsp](https://github.com/prabirshrestha/vim-lsp) plugin and config to your `.vimrc` (note: `pylsp` is *not* necessary).
What are some alternatives?
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
ale - Check syntax in Vim/Neovim asynchronously and fix files, with Language Server Protocol (LSP) support
YouCompleteMe - A code-completion engine for Vim
python-lsp-server - Fork of the python-language-server project, maintained by the Spyder IDE team and the community
vim-lsc - A vim plugin for communicating with a language server
jedi-language-server - A Python language server exclusively for Jedi. If Jedi supports it well, this language server should too.
VimCompletesMe - You don't Complete Me; Vim Completes Me! A super simple, super minimal, super light-weight tab completion plugin for Vim.
omnisharp-vim - Vim omnicompletion (intellisense) and more for C#
ccls - C/C++/ObjC language server supporting cross references, hierarchies, completion and semantic highlighting
nvim-lspconfig - Quickstart configs for Nvim LSP
emmet-vim - emmet for vim: http://emmet.io/
terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.