Neovim-from-scratch VS rust-analyzer

They also provide a "from-scratch" option, to be easier to understand

I would recommend the Neovim from Scratch series on Youtube with the addition of the code_runner.nvim plugin. It's a good config that will teach you a lot about configuring Neovim. code_runner.nvim is a nice addition, especially for a university student. Good luck!

I don't know myself how I learned neovim, but I started with using a repo called Neovim-from-scratch, but I'm not sure if it's still up to date, but I used it as my base config then started to add plugins I want and remove plugins I don't need. Most of the people recommend kickstart.nvim now as base config for neovim lua config.

Hey So I am trying to setup the neovim config for gopls and ts-server using [this](https://github.com/LunarVim/Neovim-from-scratch/tree/06-LSP), Now I would like to clarify that I have copy pasted from this guys repo and I do understand what he is doing to some extent. But for some reason in the file `lua/user/lsp/handlers.lua` He creted the following function ```lua local function lsp_keymaps(bufnr)

This is the GitHub repo for the aforementioned playlist.

I would recommend LazyVim or Kickstart.nvim. If you don't want to do any configuration, LunarVim might be for you. I would recommend the Neovim from Scratch config since it is very good and essentially has an accompanying guide. However, it is slightly out of date and needs a few tweaks to work properly.

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