neo-tree-diagnostics.nvim
A diagnostics source for neo-tree.nvim (by mrbjarksen)
nvim-lsp-installer
Further development has moved to https://github.com/williamboman/mason.nvim! (by williamboman)
neo-tree-diagnostics.nvim | nvim-lsp-installer | |
---|---|---|
3 | 82 | |
93 | 2,022 | |
- | - | |
4.6 | 9.7 | |
3 months ago | over 1 year ago | |
Lua | Lua | |
MIT License | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
neo-tree-diagnostics.nvim
Posts with mentions or reviews of neo-tree-diagnostics.nvim.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-08-01.
-
This Week In Neovim #3 — Mon Aug 01 2022
One clarification: Neo-tree has been out for longer than a couple of weeks. 1.0 was released on Jan 1. It's neo-tree-diagnostics.nvim that has been out for a couple of weeks.
-
neo-tree-diagnostics.nvim - A diagnostics source for neo-tree.nvim
The excellent neo-tree.nvim recently added support for external sources, and, conveniently enough, I was working on a source for diagnostics around the same time. I've spent a bit of time polishing it, but I think I'm confident enough now to share it with you guys. Here's a link.
-
Another coc.nvim vs native lsp post
What native LSP gives you is an entire ecosystem of plugins that integrate with that built in LSP but would not work with CoC. I created a plugin called Neo-tree that includes a file browser that will show LSP diagnostic symbols next to files. There is also a brand new external source to show a diagnostic error list which is pretty nice: https://github.com/mrbjarksen/neo-tree-diagnostics.nvim
nvim-lsp-installer
Posts with mentions or reviews of nvim-lsp-installer.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-11-09.
- [Neovim] Présentation de mason.nvim
-
Unable to get a working setup for lsp
I had previous gotten a working setup with https://github.com/williamboman/nvim-lsp-installer however, I have been unable to get it working ever since.
-
How do you stay up-to-date on the plugins you use?
The only way to stay up to date, is when you read the commits if you update the plugins. In this case for the lsp-installer in the commit bfa74f4 was mentioned that the plugin will no longer maintained
-
LSP question: manage an already installed server (instead of using lspinstall)
A word of caution, I believe lspinstall has been deprecated in favor of nvim-lspinstall which itself has also been deprecated in favor of mason-lspconfig
-
AstroNvim 2.4
We have now migrated from nvim-lsp-instasller to mason which provides automatic LSP and null-ls configuration after installation
-
Best way to go about installing LSP today?
nvim-lsp-installer or mason.nvim. FYI lsp-zero also uses mason.nvim for managing installation.
-
Vue + Volar = Error Request initialize failed
I'm using nvim-lsp-installer it installs typescript when installing volar. So I had given it that path. Plus I had typescript locally installing since I'm using vue3+ts(vite) template
-
rust-analyzer changelog #146
Though mason only recently replaced nvim-lsp-installer. Same author but they decided to make a complete rewrite given the broader scope beyond only providing language servers. And nvim-dap had it's initial release in late July. The actual dap servers are all kind of mature since they've been running on vscode for a couple of years or more now - and the protocol is apparently almost as old as lsp. So when I call them beta, it's more a commentary on the state of the neovim side of the ecosystem. If you mess around getting nvim-dap to work then there's a chance things might change over the coming months and you might have to return to configuring it more often than you'd like. In this sense for now I'm happy just to open vscode or another more appropriate IDE to debug. But I can see myself using the plugins in a year or two when they've matured.
-
Is there any way to autocomplete language functions? For example, show things like fmt.Printf or fmt.Println when writing fmt.Print and pressing the autocomplete key.
Here are a few resources to get you started: 1. https://github.com/neovim/nvim-lspconfig 1. https://github.com/golang/tools/tree/master/gopls 1. https://github.com/williamboman/nvim-lsp-installer
-
rust_tools equivalent for C Sharp
Can recommend a combination of omnisharp-roslyn native LSP (installed manually or through something like mason or nvim-lsp-installer) with omnisharp-vim for some extra C#-niceties like OmniSharpRunTest, etc.