Issues with rust-analyzer configuration

[diegofariasm]

Issues with rust-analyzer server config

Mostly all of the problems related to c++ and rust have been solved with the latest commits, but there a few new problems with the rust-analyzer server configuration; which are really weird to be honest.

I though this would be a nixos related issue because of the origin of the error, but i have tried the nyoom config in a few different distros and have gotten the same problem.

First glitch

This first glitch happens in a specific case in which the rust file you are editing already exists. For some reason, neovim will then complain about the configuration for rust-analyzer

Bug output:

[lspconfig] Cannot access configuration for rust_analyzer. Ensure this server is listed in server_configurations.md or added as a custom server.

Steps to reproduce

1+ Create a new rust file ( Can be any name, will refer to as main.rs) 2+ Edit said file

Second glitch

This glitch happens most of the times, although sometimes it won't actually happen. As it happens on 80%+ of cases, i haven't actually figured out what causes the issue. I also didn't figure anything by trying to find the message the lsp's logs. *Maybe some missing tooling for rust?

Steps to reproduce

1- Edit any rust file 2- Wait while rust-standalone scans the roots

[shaunsingh]

1. Thanks, will look into it
2. Second issue stems from https://github.com/Olical/conjure/issues/401, I think I'll either disable conjure for rust, or gate it behind a +excvr flag