language-server-protocol
vim-lsp-ale
Our great sponsors
language-server-protocol | vim-lsp-ale | |
---|---|---|
121 | 10 | |
10,675 | 82 | |
2.0% | - | |
8.7 | 0.0 | |
7 days ago | over 2 years ago | |
HTML | Vim Script | |
Creative Commons Attribution 4.0 | 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.
language-server-protocol
-
Ollama is now available on Windows in preview
But these are typically filling the usecases of productivity applications, not ‘engines’.
Microsoft Word doesn’t run its grammar checker as an external service and shunt JSON over a localhost socket to get spelling and style suggestions.
Photoshop doesn’t install a background service to host filters.
The closest pattern I can think of is the ‘language servers’ model used by IDEs to handle autosuggest - see https://microsoft.github.io/language-server-protocol/ - but the point of that is to enable many to many interop - multiple languages supporting multiple IDEs. Is that the expected usecase for local language assistants and image generators?
-
The Mechanics of mutable and immutable references in Rust
If you tried writing code like the one above, your Rust LSP should already be telling you that what you're doing is unacceptable:
-
A guide on Neovim's LSP client
A language server is an external program that follows the Language Server Protocol. The LSP specification defines what type of messages a language server can receive, and also how it should respond. The idea here is that any tool that follows the LSP specification can communicate with a language server.
-
The IDEs we had 30 years ago and we lost
> There's a strange dance of IDEs coming and going, with their idiosyncracies and partial plugins.
The Language Server Protocol [1] is the best thing to happen to text editors. Any editor that speaks it gets IDE features. Now if only they'd adopt the Debug Adapter Protocol [2]...
[1] https://microsoft.github.io/language-server-protocol/
[2] https://microsoft.github.io/debug-adapter-protocol/
-
The More You Gno: Gno.land Monthly Updates - 6
The Gno Language Server (gnols) is an implementation of the Language Server Protocol (LSP) for the Gno programming language. It is similar to the equivalent “gopls” project for Go, as they can be plugged into your code editor through extensions and allow you to access handy features, such as autocompletion, formatting, and compile-time warnings/errors. Gnols makes writing code simpler, working with several editors to suit your preferences. To try it out, visit the CONTRIBUTING.md file, which contains instructions to get you started. Our current documentation targets Vim, Neovim, and SublimeText, but can likely be used with any editor that supports LSP. Feel free to contribute to improving Gnols and adding more features. It’s well-written, and simple to dive into the code and add more capabilities.
-
LSP could have been better
Honestly, you should read some of the docs [0] if these are the sorts of questions you're asking.
[0] https://microsoft.github.io/language-server-protocol/
-
Show HN: Postgres Language Server
hey HN. this is a Language Server[0] designed specifically for Postgres. A language server adds features to IDEs (VSCode, NeoVim, etc) - features like auto-complete, go-to-definition, or documentation on hover, etc.
there have been previous some attempts at adding Postgres support to code editors. usually these attempts implement a generic SQL parser and then offer various "flavours" of SQL.
This attempt is different because it uses the actual Postgres parser to do the heavy-lifting. This is done via libg_query, an excellent C library for accessing the PostgreSQL parser outside of the server. We feel this is a better approach because it gives developers 100% confidence in the parser, and it allows us to keep up with the rapid development of Postgres.
this is still in early development, and mostly useful for testers/collaborators. the majority of work is still ahead, but we've verified that the approach works. we're making it public now so that we can develop it in the open with input from the community.
a lot of the credit belongs to pganalyze[1] for their work on libg_query, and to psteinroe (https://github.com/psteinroe) who the creator and maintainer of the LSP.
[0] LSP: https://microsoft.github.io/language-server-protocol/
[1] pganalyze: https://pganalyze.com/
-
Refactoring tools
See: https://github.com/microsoft/language-server-protocol/issues/1164
-
Nx Console gets Lit
The nxls is a language server based on the Language Server Protocol (LSP) and acts as the “brain” of Nx Console. It analyzes your Nx workspace and provides information on it, including code completion and more.
-
How to configure vim like an IDE
LSP stands for "Language Server Protocol", which defines how a language server and an editor (client) can communicate to provide code navigation, completion, etc. (source). Traditional IDE's would have something similar to this baked-in already, but proprietary to their software/language; whereas LSP is an open standard, so anything could implement it.
vim-lsp-ale
-
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.
-
Where to start with LSP in Vim?
Don't you need vim-lsp-ale for that? It puts lint results from vim-lsp into ALE's interface so ALE doesn't need to run a second lsp server. Which seems to be another way of saying ALE uses it as a source.
-
[plugin woes] Any vim-lsp-ale alternatives for built-in lsp client?
However; apparently this causes two LSP's to run. Instead of nvim's default lsp; there is also prabirshrestha/vim-lsp and mattn/vim-lsp-settings that runs LSP's. There is rhysd/vim-lsp-ale to fix the concurrent LSP running between Ale and vim-lsp, and shun/ddc-vim-lsp which integrates vim-lsp with ddc.vim
-
How can I make VIM autocomplete similar to VSCode in macos
See comment here for a setup with vim-lsp. Add ale for lint support and vim-lsp-ale to put lsp linting into ale.
-
What pains me the most about C : Having to update headers any time I change a function prototype
ALE is primarily for linting (although it may also serve as basic LSP client). The protocol itself is for code completion, hover tips, navigation, workspace symbols, finding references, highlighting, renaming, reformatting, refactoring etc. And also diagnostics (which you can integrate with ALE via vim-lsp-ale).
-
PLS: Perl Language Server - vim integration help request
I looked at this earlier and was unsure if this is in lieu of ALE or in addition to ALE. I saw a post about also needed - How can I use ALE and vim-lsp together? When I looked into vim-lsp-ale I was unsure about how to configure PLS for perl.
-
Trying a IDE like on Vim after a week to setup Emacs (kind of fail).
Try vim-lsp-ale to get vim-lsp lint errors to show in ale. You should turn off all other linters unless you actually need them.
-
Solution for "Go To Definition"
Sorry I should have mentioned I'm using ALE for linting/fixing. Would I have to remove ALE to use Neovim's native LSP, or use a plug-in like this I'm assuming?
-
Vim is the #4 most loved editor with a 70% rating, according to the 2021 Stackoverflow Developer Survey (Neovim is #1, VSCode #2)
To me "integrated" means I do everything from one application -- no building in the shell etc. I think the biggest knock against "integrated" is when vim plugins don't work together (like ale and lsp before vim-lsp-ale).
-
vim-lsp + ALE bridge
Hello! I thought I'd mention this plugin to people, as people might not know about it. rhysd on GitHub has put together a plugin that connects vim-lsp to ALE, completely without much, if any, help from me. I think it's pretty cool, and it could be useful for someone. Check it out.
What are some alternatives?
intellij-lsp-server - Exposes IntelliJ IDEA features through the Language Server Protocol.
syntastic - Syntax checking hacks for vim
tree-sitter-org - Org grammar for tree-sitter
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
omnisharp-server - HTTP wrapper around NRefactory allowing C# editor plugins to be written in any language.
asyncomplete-lsp.vim
tree-sitter - An incremental parsing system for programming tools
cscope_maps.nvim - For old school code navigation. Adds cscope support to Neovim 0.9+.
magic-racket - The best coding experience for Racket in VS Code
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
friendly-snippets - Set of preconfigured snippets for different languages.
nvim-ale-diagnostic - Display Neovim LSP diagnostics in ALE.