neovim-ui
vim-lsp
neovim-ui | vim-lsp | |
---|---|---|
5 | 81 | |
83 | 3,019 | |
- | - | |
0.0 | 6.4 | |
about 3 years ago | 12 days ago | |
Lua | Vim Script | |
GNU General Public License v3.0 or later | 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.
neovim-ui
- Posibility of UI library for neovim?
-
Neovim - Build UI using nui.nvim
mjlbach/neovim-ui
-
Neovim v0.5
I understand the frustration (making neovim more cohesive is definitely a goal). It sounds like coc provides the UI you are used to, so there's no harm in sticking with that!
Many of our users explicitly don't want automatically called functions that would slow down the editor (autocommands that map signature requests to the language server, for example), so by nature neovim's core implementation is extremely conservative.
One thing I would like to do, is make the automatic pop-ups for signature easier to implement with our current handler, which means a plugin like signature-x could use our upcoming lsp.config option to configure it's borders (https://github.com/neovim/neovim/pull/14681), and match the rest of the UI.
I also have another project I was working on before the 0.5 stabilization phase (https://github.com/mjlbach/neovim-ui). The goal with this is to have composable/overridable UI elements built into core (which we would use for our internal lsp functions), that can be used (or overridden) by UI plugins.
In summary, I think the likelihood of autocompletion (and generally auto-anything) being built-into core is very small, but providing the APIs in neovim core to make snippets - autocompletion - automated UI elements easier for plugin authors is a high priority.
-
Plugin unification
Yep, I started working on this awhile ago https://github.com/mjlbach/neovim-ui but put it on hold for 0.5 stabilization.
-
status of neovim popup windows
I am working on this, but it will probably have to wait until after the 0.5 release (I don't know when this will be). This is part of the larger UI effort in neovim-ui which is currently glorified vaporware. As far as I know, TJ, Smolck, and I are the only ones who have expressed interest in fixing this.
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?
popup.nvim - [WIP] An implementation of the Popup API from vim in Neovim. Hope to upstream when complete
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
nui.nvim - UI Component Library for Neovim.
ale - Check syntax in Vim/Neovim asynchronously and fix files, with Language Server Protocol (LSP) support
guihua.lua - A GUI library for Neovim plugin developers
YouCompleteMe - A code-completion engine for Vim
TypeScriptToLua - Typescript to lua transpiler. https://typescripttolua.github.io/
python-lsp-server - Fork of the python-language-server project, maintained by the Spyder IDE team and the community
nvim-lspconfig - Quickstart configs for Nvim LSP
vim-lsc - A vim plugin for communicating with a language server
nvim-lsputils - Better defaults for nvim-lsp actions
jedi-language-server - A Python language server exclusively for Jedi. If Jedi supports it well, this language server should too.