LanguageClient-neovim
Language Server Protocol (LSP) support for vim and neovim. (by autozimu)
tree-sitter-rust
Rust grammar for tree-sitter (by tree-sitter)
Our great sponsors
LanguageClient-neovim | tree-sitter-rust | |
---|---|---|
11 | 8 | |
3,536 | 300 | |
- | 4.3% | |
0.0 | 7.7 | |
5 months ago | 18 days ago | |
Rust | JavaScript | |
MIT License | MIT License |
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?
-
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!
-
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?
I think https://github.com/autozimu/LanguageClient-neovim has this feature already implemented. Built-in LSP could support it also as soon as somebody takes the effort to issue and process the necessary requests.
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.
tree-sitter-rust
Posts with mentions or reviews of tree-sitter-rust.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-20.
-
Topiary: A code formatting engine leveraging Tree-sitter
Yes. It's typically a fair bit slower than a hand-coded parser. The idea sounds great until you're working on a codebase with 2 million LOC. At that point, the speed of a cold parse is most important, whereas TS is designed for fast re-parsing of a single file. These aren't great numbers but the Rust TS parser is reportedly 2x slower than rustc's https://github.com/tree-sitter/tree-sitter-rust. It's no surprise that you just use the faster option if it's convenient.
-
Emacs and Java Development: Corfu + Cape + LSP-Mode + Treesit
(use-package treesit :ensure nil :custom ;; Some stuff taken from here: https://robbmann.io/posts/emacs-treesit-auto/ (treesit-extra-load-path '("/usr/lib64/")) (treesit-language-source-alist '((bash . ("https://github.com/tree-sitter/tree-sitter-bash")) (c . ("https://github.com/tree-sitter/tree-sitter-c")) (c++ . ("https://github.com/tree-sitter/tree-sitter-cpp")) (csharp . ("https://github.com/tree-sitter/tree-sitter-c-sharp")) (css . ("https://github.com/tree-sitter/tree-sitter-css")) (elixir ("https://github.com/elixir-lang/tree-sitter-elixir")) (html . ("https://github.com/tree-sitter/tree-sitter-html")) (java . ("https://github.com/tree-sitter/tree-sitter-java")) (javascript . ("https://github.com/tree-sitter/tree-sitter-javascript")) (json . ("https://github.com/tree-sitter/tree-sitter-json")) (lua . ("https://github.com/Azganoth/tree-sitter-lua")) (makefile . ("https://github.com/alemuller/tree-sitter-make")) (org . ("https://github.com/milisims/tree-sitter-org")) (python . ("https://github.com/tree-sitter/tree-sitter-python")) (tsx . ("https://github.com/tree-sitter/tree-sitter-typescript" "master" "tsx/src")) (typescript . ("https://github.com/tree-sitter/tree-sitter-typescript" "master" "typescript/src")) (ruby . ("https://github.com/tree-sitter/tree-sitter-ruby")) (rust . ("https://github.com/tree-sitter/tree-sitter-rust")) (sql . ("https://github.com/m-novikov/tree-sitter-sql")) (toml . ("https://github.com/tree-sitter/tree-sitter-toml")) (yaml . ("https://github.com/ikatyang/tree-sitter-yaml")))) (major-mode-remap-alist '((c-mode . c-ts-mode) (c++-mode . c++-ts-mode) (csharp-mode . csharp-ts-mode) (css-mode . css-ts-mode) (html-mode . html-ts-mode) (java-mode . java-ts-mode) (js-mode . js-ts-mode) (json-mode . json-ts-mode) (makefile-mode . makefile-ts-mode) ;; (org-mode . org-ts-mode) ;; not mature yet (python-mode . python-ts-mode) (typescript-mode . typescript-ts-mode) (ruby-mode . ruby-ts-mode) (rust-mode . rust-ts-mode) (toml-mode . toml-ts-mode) (yaml-mode . yaml-ts-mode))) (treesit-auto-fallback-alist '((toml-ts-mode . conf-toml-mode) (typescript-ts-mode . nil) (tsx-ts-mode . nil))) (treesit-font-lock-settings t) (treesit-simple-indent t) (treesit-defun-type-regexp t)) (use-package treesit-auto :demand t :config (setq treesit-auto-install t) (global-treesit-auto-mode))
- Building tree-sitter languages for Emacs
-
Is it possible to have Rust doc test comments highlighted in Neovim?
Notes for anyone interested, there is this PR https://github.com/tree-sitter/tree-sitter-rust/pull/128, which merges successive doc comments.
-
Rust and Neovim - A Thorough Guide and Walkthrough
Tree-sitter is a fantastic parser generation and incremental parsing library, that supports Rust language bindings and has an available parser Rust tree-sitter-rust.
-
Plugins to help writing a new tree-sitter parser?
You can see a much more in-depth version at https://github.com/tree-sitter/tree-sitter-typescript or https://github.com/tree-sitter/tree-sitter-rust
-
Is rust-analyzer for neovim ever going to support semantic syntax highlighting?
I'll be really interested to see what folks end up preferring once nvim 0.5 ships with treesitter support. Do folks have any experience with the Rust grammar?
What are some alternatives?
When comparing LanguageClient-neovim and tree-sitter-rust you can also consider the following projects:
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
nvim-lspconfig - Quickstart configs for Nvim LSP
vim-easy-align - :sunflower: A Vim alignment plugin
rust-analyzer - A Rust compiler front-end for IDEs
vim-lsp - async language server protocol plugin for vim and neovim
nvim-treesitter - Nvim Treesitter configurations and abstraction layer
clangd - clangd language server
tree-sitter-graphql - Treesitter grammar for GraphQL
tagbar - Vim plugin that displays tags in a window, ordered by scope
rust-analyzer - A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer]
neovide - No Nonsense Neovim Client in Rust