packspec
nvim-lspconfig
packspec | nvim-lspconfig | |
---|---|---|
7 | 523 | |
205 | 9,585 | |
2.0% | 2.8% | |
4.8 | 9.7 | |
3 months ago | 5 days ago | |
Lua | Lua | |
Apache License 2.0 | Apache License 2.0 |
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.
packspec
- This Week In Neovim #31 – Mon Feb 13 2023
-
Introducing Luarocks-Tag-Release - Publish your Neovim plugins to LuaRocks
It looks like there's a WIP package specification that might also support source = luarocks://.
-
Standardizing Neovim package management API - could or should this be a thing? Let’s talk about it!
I was hoping you would clarify exactly what you're proposing so I could forward the appropriate link, otherwise I'm just guess based off a vague (but long) post. Based on other replies in this reddit post, I'm not the only one confused by your ambiguous and likely incorrect terminology. It sounds like you're looking for a specification, which exists https://github.com/nvim-lua/nvim-package-specification, it just isn't well adopted. There's also countless Github issues and discussions about this on IRC which you could find by a simple Google search. It really just depends on what you're alluding to which is why I linked what an API was so you could be more specific. If you're looking for the plugin managers API (notice the qualifier) to be consistent, then that's not a good idea since the API of the plugin manager is what differentiates them, it's like saying all programming languages should be the same, the only thing different should be the backend (e.g. gcc vs llvm). The consistency should be at a different layer (thus the plugin spec).
-
Breaking changes inbound (next few weeks) for lspconfig and neovim's language server client lsp
packspec, a package specification for neovim to address the dependency issue
-
Opinion on better plugin management?
There is an issue for it: https://github.com/nvim-lua/nvim-package-specification/issues/23
nvim-lspconfig
-
JetBrains' unremovable AI assistant meets irresistible outcry
I suggest looking for blog posts about this, you're gunnuh wanna pick out a plugin manager and stuff. It's kind of like a package manager for neovim. You can install everything manually but usually you manually install a plugin manager and it gives you commands to manage the rest of your plugins.
These two plugins are the bare minimum in my view.
https://github.com/nvim-treesitter/nvim-treesitter
Treesitter gives you much better syntax highlighting based on a parser for a given language.
https://github.com/neovim/nvim-lspconfig
This plugin helps you connect to a given language LSP quickly with sensible defaults. You more or less pick your language from here and copy paste a snippet, and then install the relevant LSP:
https://github.com/neovim/nvim-lspconfig/blob/master/doc/ser...
For Python you'll want pylsp. For JavaScript it will depend on what frontend framework you're using, I probably can't help you there.
pylsp itself takes some plugins and you'll probably want them. https://github.com/python-lsp/python-lsp-server
Best of luck! Happy hacking.
-
Neovide – a simple, no-nonsense, cross-platform GUI for Neovim
Adding language support it neovim isn't very difficult once you're setup. I use nvim-lspconfig[1] and just about any language you could need is documented[2]. But like others have mentioned there are batteries included distributions of neovim if that's your cup of tea.
[1]: https://github.com/neovim/nvim-lspconfig/
[2]: https://github.com/neovim/nvim-lspconfig/blob/master/doc/ser...
-
A guide on Neovim's LSP client
If we can't find the basic usage in the documentation we can go to nvim-lspconfig's github repository. In there we look for a folder called server_configurations, this contains configuration files for a bunch of language servers.
-
Do I need NeoVIM?
https://github.com/hrsh7th/nvim-cmp This is an autocompletion engine https://github.com/nvim-treesitter/nvim-treesitter This allows NeoVim to install parsing scripts so NeoVim can do things like code highlighting. https://github.com/williamboman/mason.nvim Not strictly necessary, but allows you to access a repo of LSP, install them, and configure them for without you actively messing about in config files. https://github.com/neovim/nvim-lspconfig Also not strictly necessary, but vastly simplifies LSP setup. https://github.com/williamboman/mason-lspconfig.nvim This lets the above two plugins talk to each other more easily.
-
cpp setting problem
This specific issue talks about fixing clangd for that error: https://github.com/neovim/nvim-lspconfig/issues/2184. The issue is ongoing for ccls AFAIK but for clangd, this has been discussed and fixed in the past already.
-
Need help to set up the pbkit language server
I am trying to set up the pbkit language server for protobuf files. Since it is not part of the nvim-lspconfig repo's server configurations, I have to figure the way out myself. It doesn't seem to be too difficult, as I can start from the bufls configuration there. The following is what I have at the moment:
-
Option omnifunc is not set
I have configured neovim with lspconfig and mason. Added the suggested configuration of the lsp config(https://github.com/neovim/nvim-lspconfig) to ~/.config/nvim/after/plugin/lsp.lua Then I installed via mason the following language servers:
-
Using nvim-lint as a null-ls alternative for linters
Personally, i think nvim-lint is the best alternative currently, specially so because it has no dependencies on external binaries. This guide assumes you already have your LSP set up with nvim-lspconfig (or an alternative like lsp-zero). You should also have an way to install the linters you are gonna need, i highly recommend Mason with mason-lspconfig.
-
The Future of the Vim Project
Basically neovim can act as a client to a variety of different language servers (https://github.com/neovim/nvim-lspconfig/blob/master/doc/ser...) which give neovim IDE capabilities. This can be done in original Vim also but requires external plugins which can be a pain to compile and install. Neovim has it built in.
-
SQL LSP dialect
I'm struggling to get [sqlls](https://github.com/joe-re/sql-language-server) with [nvim-lspconfig](https://github.com/neovim/nvim-lspconfig) to use Postgres syntax.
What are some alternatives?
lazy.nvim - 💤 A modern plugin manager for Neovim
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
nvim-conf - ☄ Maddison's Neovim configuration!
null-ls.nvim - Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.
luarocks - LuaRocks is the package manager for the Lua programming language.
nvim-lsp-installer - Further development has moved to https://github.com/williamboman/mason.nvim!
vscode-eslint - VSCode extension to integrate eslint into VSCode
nvim-jdtls - Extensions for the built-in LSP support in Neovim for eclipse.jdt.ls
lsp-format.nvim - A wrapper around Neovims native LSP formatting.
coc - Chroniques Oubliées Contemporain
neovim - Vim-fork focused on extensibility and usability
ale - Check syntax in Vim/Neovim asynchronously and fix files, with Language Server Protocol (LSP) support