rust-analyzer VS vim-lsp-settings

go build 3.62s user 0.76s system 171% cpu 2.545 total

I was looking forward to parallel front-end[4], but I have not seen any improvement for these small changes.

[1]: https://github.com/rust-lang/rust-analyzer

For example, intelephense can show diagnostics in real time, there is no need to save the file to get new diagnostics. But rust-analyzer, the language server for rust, can only update diagnostics after saving the file.

6. Rust Analyzer

The rust-analyzer readme suggests you go here for support request. But even there, you'll need to provide more details to get useful help.

For example: https://github.com/rust-lang/rust-analyzer/blob/master/docs/...

> If you create an LSP, it will work best in VS Code.

Any editor can work just as well as (or even better than) VS Code.

So, apparently the reason why rust-analyzer, the LSP server for Rust does not have persistent caching is because it would make "optimizing initial passes less important".

All I want to know is: Will it have a build configuration pulldown?

I am not a Rust dev. It surely looks great.

However, from what I understand it seems to supply just a parser separate from the Rust compiler (https://github.com/rust-lang/rust-analyzer/tree/master/crate...) trying to keep up with Rust‘s development. So, in principle, it could have been just another treesitter parser plugin, too.

So, again, the LSP framework does not directly provide any magical benefit over a static parsing framework. All the semantic analysis capabilities stem from a good parser.

rust-analyzer > manual > helix > binary > rustup component add rust-analyzer

I am reading here but still... it seems all OK. It is weird that it was working with ALE with the current setup. Anyway, I noticed that every once in a while I get this error when I change buffer.

There's https://github.com/mattn/vim-lsp-settings to save even more lines, which is I think what OP wants.

vim-lsp-settings makes installing lsp for vim-lsp trivial: :LspInstallServer

Hello everyone, I have this problem when using vim-lsp-settings, that every time my cursor passes through a word (sorry I don't have enough information to derive what type of word, but take Type, Function in Python, or constants (like g:lsp_diagnostics_signs_enabled) and has() in vimrc) it always showing similar occurrences of the word, and I don't want that. Not only it takes some time (highlighting that word cursor is on, and when moving cursor really fast it couldn't catch up), it's usually something I don't really need (well, if it could be configured to be faster and my laptop won't screeching then I'm all in - I'm using thinkPad x270).

I use vim-lsp plugin which only needs a few lines of config. It has several JavaScript language servers listed in vim-lsp-settings.

Then lsp. All four of these: prabirshrestha/vim-lsp; mattn/vim-lsp-settings; prabirshrestha/asyncomplete.vim; prabirshrestha/asyncomplete-lsp.vim

vim-lsp that can be bootstrapped with vim-lsp-settings, for jumping to definitions, etc.