Ah, you’re right, and I knew that existed, but I’m concerned this doesn’t show all of the config for VSCode, because the settings UI version has 3 separate sections for normal, WSL remote, and workspace.
Furthermore, it seems like rust-analyzer tends to dwell on some crate, and when I go visit a new crate cloned from GitHub in another directory path, rust-analyzer doesn’t find it, just keeps looking for the old stuff.
A chain of fd + rg finds a lot of hidden state for VSCode and this is just the stuff on the WSL2 Ubuntu side and not even including the hidden state on the Windows side.
I just feel like rust analyzer is really cool and probably works great but I’m constantly struggling with getting it pointed in the right direction and the vs code extension is super hard to debug because it’s really unclear about what folders it’s looking at for Cargo.toml files and why. You can stop, start, restart, etc, in the clicky context menu, but that doesn’t solve issues like “please analyze this crate at path X” or “I changed the path to crate Y” … and the docs for RA seem to indicate you have to set an env var to get info level logs, which seems odd, isn’t info the standard debug level? Even if the RA log level is set higher than info, it seems like “here’s where we analyze” and “here’s where you’re telling us what to analyze” are critical level logs (aka, always print this stuff to stdout, no need to change log levels, the key input configuration is higher priority than info or debug level logs)
Really, I wish the rust analyzer VSCode extension would be more clear about how to tell it what paths to analyze and where exactly it finds that configuration declaration file(s). Right now it seems like you need to set some environment variable just to get any info on this aspect (silly) and then the info you get is an unreadable wall of json, really, rust is such a cool language and this just sucks the fun out of it, it feels like dealing with some random JavaScript module esm webpack babel crap, not the level of reliability and correctness I expect from a Rust project, especially one as valuable and critical to the whole community as Rust Analyzer.
If any devs of the VSCode experience for RA read this, then I hope you’ll take some time to make sure it’s really easy to click on the rust analyzer button and see where exactly rust analyzer is analyzing and how to reconfigure the paths under analysis!