LanguageClient-neovim
Language Server Protocol (LSP) support for vim and neovim. (by autozimu)
rust-analyzer
A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer] (by rust-analyzer)
LanguageClient-neovim | rust-analyzer | |
---|---|---|
11 | 207 | |
3,541 | 9,320 | |
- | - | |
0.0 | 10.0 | |
6 months ago | about 2 years ago | |
Rust | Rust | |
MIT License | GNU General Public License v3.0 or later |
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.
LanguageClient-neovim
Posts with mentions or reviews of LanguageClient-neovim.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-06-09.
- Where to start with LSP in Vim?
-
Simple plugin to display tag under cursor in popup (Vim 8.2+)
i know the language client neovim has such a function (:help languageclient_textdocument_codelens after compiling its helptags). AFAIK you can get that running in Vim 8, but not sure.
-
F# for Linux People
On NeoVim, the built-in LSP client works without modification. On Vim, you will need LanguageClient-neovim.
-
Just wanted to share my enthusiasm when I realised error checking (clangd) could be so fast! :) It's almost instant...
I'm using LanguageClient-neovim. Here's the relevant portions of my init.vim:
-
Using Vim for Everything!
I just saw a nice post in /u/medwatt about using vim for VHDL/Verilog and thought I'd contribute a little! * Syntax and error highlight: https://github.com/autozimu/LanguageClient-neovim * Column align: https://github.com/junegunn/vim-easy-align * Remove annoying whitespaces: https://github.com/ntpeters/vim-better-whitespace * Partial (fuzzy) filename search: https://github.com/junegunn/fzf.vim * Outline all declarations inside a file: ⠀https://github.com/preservim/tagbar * Treat indentations as vim-objects (useful for languages that don't use { }): https://github.com/michaeljsmith/vim-indent-object There is also mouse support in vim for those who want it. Try typing :set mouse=a. Very useful for resizing windows. I also highly recommend you get good at using folds (https://vim.fandom.com/wiki/Folding). It makes it a LOT easier to navigate files. You can save your fold config per-file with :mkview and load it later with :loadview. If I come up with more hints - I'll mention them in the comments!
-
Neovim's built-in LSP with Ruby and Rails
I've been using LanguageClient and solargraph gem with plain Vim 8 for a long time already. Still, having a bit better experience at Ruby coding with Emacs and its lsp-mode & company & inf-ruby combo.
-
ALE vs YouCompleteMe vs CoC-rust vs LanguageClient-neovim
Might migrate to Neovim's native LSP support at some point, however I find vim-lsp more feature complete out of the box. I used to use LanguageClient-neovim, however, I missed proper support for signature help.
-
Is there a difference between a LSP, code completer, and a linter?
YCM is a client. The client is a plugin for Vim or Neovim, even the "built-in" client in Neovim is just a Lua plugin that is included with the editor, it's not really built-in. Examples of other clients:LanguageClient-neovim, vim-lsp, ale.
-
Is rust-analyzer for neovim ever going to support semantic syntax highlighting?
LanguageClient-neovim just merged some support for semantic tokens and the plan, as I read the PR/issues, is to next implement some default mappings from the semantic tokens to highlight groups.
-
Which lsp client is best ?
The best LSP client is the one that works for you. When it comes to neovim, there is a generous variety of LSP clients to choose from. The notables ones being vim-lsc and vim-lsp written in vimscript, LanguageClient-neovim written in rust, YouCompleteMe is written in python and in my experience is the hardest to install, coc.nvim written in typescript and, of course, the neovim's built-in one. I would recommend going with coc.nvim, as it is the best LSP client right now, though it provides much more features than a standard lsp client does and for some people it is a disadvantage and for the others it's not. Also you have to install node.js on your system for coc.nvim to work. I myself use neovim built-in one for a few reasons: it's not in stable yet, but when the neovim 0.5 version comes out, it is gonna be the standard client. Another reason is it's extremely lightweight and customizable. There were already several discussions on the subreddit about the clients you can check out.
rust-analyzer
Posts with mentions or reviews of rust-analyzer.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-17.
-
rust-analyzer changelog #177
#14561 map tokens from include! expansion to the included file
-
Make LSP-Rust-analyzer works
return { tools = { -- autoSetHints = false, on_initialized = function() vim.api.nvim_create_autocmd({ "BufWritePost", "BufEnter", "CursorHold", "InsertLeave" }, { pattern = { "*.rs" }, callback = function() vim.lsp.codelens.refresh() end, }) end, auto = false, inlay_hints = { -- Only show inlay hints for the current line only_current_line = false, auto = false, -- Event which triggers a refersh of the inlay hints. -- You can make this "CursorMoved" or "CursorMoved,CursorMovedI" but -- not that this may cause higher CPU usage. -- This option is only respected when only_current_line and -- autoSetHints both are true. only_current_line_autocmd = "CursorHold", -- whether to show parameter hints with the inlay hints or not -- default: true show_parameter_hints = false, -- whether to show variable name before type hints with the inlay hints or not -- default: false show_variable_name = false, -- prefix for parameter hints -- default: "<-" -- parameter_hints_prefix = "<- ", parameter_hints_prefix = " ", -- prefix for all the other hints (type, chaining) -- default: "=>" -- other_hints_prefix = "=> ", other_hints_prefix = " ", -- whether to align to the lenght of the longest line in the file max_len_align = false, -- padding from the left if max_len_align is true max_len_align_padding = 1, -- whether to align to the extreme right or not right_align = false, -- padding from the right if right_align is true right_align_padding = 7, -- The color of the hints highlight = "Comment", }, hover_actions = { auto_focus = false, border = "rounded", width = 60, -- height = 30, }, }, server = { --[[ $ mkdir -p ~/.local/bin $ curl -L https://github.com/rust-analyzer/rust-analyzer/releases/latest/download/rust-analyzer-x86_64-unknown-linux-gnu.gz | gunzip -c - > ~/.local/bin/rust-analyzer $ chmod +x ~/.local/bin/rust-analyzer --]] -- cmd = { os.getenv "HOME" .. "/.local/bin/rust-analyzer" }, cmd = { os.getenv "HOME" .. "~/.cargo/bin/rust-analyzer" }, on_attach = require("user.lsp.handlers").on_attach, capabilities = require("user.lsp.handlers").capabilities, settings = { ["rust-analyzer"] = { lens = { enable = true, }, checkOnSave = { command = "clippy", }, }, }, }, }
-
rust-analyzer changelog #164
I would like changes like https://github.com/rust-analyzer/rust-analyzer/pull/13799 to be listed in 'Breaking Changes' category, to приманка draw the users' attention.
-
Mun v0.4.0 released
For those of you who haven’t heard of Mun before, Mun is an embeddable programming language empowering creation through iteration. The idea to create Mun originated out of frustration with the Lua dynamic scripting language and a desire to have similar hot reloading functionality available in Rust. As such, it’s not a direct competitor with Rust, but instead is intended to be used with Rust (or C/C++) as a host/embedded language pairing. Actually, Mun is completely written in Rust, building on similar crates as rust-analyzer and rustc. Its key features include:
-
rust-analyzer changelog #159
#13728 upgrade chalk to make solver fuel work again (works around most trait solving hangs).
-
rust-analyzer changelog #147
#13221 (first contribution) add option to move lenses above doc comments (rust-analyzer.lens.location):
-
Does Rust need proc-macros 2.0?
Rust-analyzer has a good overview: https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/dev/syntax.md
-
rust-analyzer changelog #134
#12517 (first contribution) fix completion for methods in trait generated by macro.
-
LSP Rust Analyzer keeps telling me `Error NO_RESULT_CALLBACK_FOUND`
-- all the opts to send to nvim-lspconfig -- these override the defaults set by rust-tools.nvim -- see https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#rust_analyzer server = { -- on_attach is a callback called when the language server attachs to the buffer -- on_attach = on_attach, settings = { -- to enable rust-analyzer settings visit: -- https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/user/generated_config.adoc ["rust-analyzer"] = { -- enable clippy on save checkOnSave = { command = "clippy" }, assist = { importGranularity = "module", importPrefix = "self", }, cargo = { loadOutDirsFromCheck = true }, procMacro = { enable = true }, } } },
-
rust-analyzer changelog #130
#12349 publish universal VSIX to make Code happy.
What are some alternatives?
When comparing LanguageClient-neovim and rust-analyzer you can also consider the following projects:
nvim-lspconfig - Quickstart configs for Nvim LSP
vscode-rust - Rust extension for Visual Studio Code
vim-easy-align - :sunflower: A Vim alignment plugin
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
vim-lsp - async language server protocol plugin for vim and neovim
intellij-rust - Rust plugin for the IntelliJ Platform
clangd - clangd language server
rustfmt - Format Rust code
tagbar - Vim plugin that displays tags in a window, ordered by scope
eglot - A client for Language Server Protocol servers
tree-sitter-rust - Rust grammar for tree-sitter
rust - Empowering everyone to build reliable and efficient software.
LanguageClient-neovim vs nvim-lspconfig
rust-analyzer vs vscode-rust
LanguageClient-neovim vs vim-easy-align
rust-analyzer vs Clippy
LanguageClient-neovim vs vim-lsp
rust-analyzer vs intellij-rust
LanguageClient-neovim vs clangd
rust-analyzer vs rustfmt
LanguageClient-neovim vs tagbar
rust-analyzer vs eglot
LanguageClient-neovim vs tree-sitter-rust
rust-analyzer vs rust