-
Notifications
You must be signed in to change notification settings - Fork 168
[CFG] rust.target_dir is broken #322
Comments
Oh, I think it was fixed in 0.4.4. |
I believe I am also experiencing the same issue. I also don't believe it has been fixed, as I am using From what I can see, it appears that Using process explorer I can see that the I am current using a Windows host with the stable channel of Rust installed through I am more than happy to gather more information if that is needed. |
After some experimenting, I have found that setting |
Fixed as of 0.6.1. |
322: Fix analyzer extension fail when there are enabled any VIM extension r=matklad a=max-frai `type` command is allowed only once to be registered and it was built specially for vim mode. So if user has vim extension enabled, rust-analyzer initialization failes on trying to register own `type` handler. Unfortunatelly, there are no nice ways to check if command is already registered so the way is to wrap everything with try/catch and notify user about conflict. Co-authored-by: frai <me@maxfrai.com>
The last release (0.4.2).
Default value for
rust.target_dir
is"rls"
, so the result dir-tree looks like this:If I set
"rust.target_dir": null
or"rust.target_dir": "target/rls"
- all is ok, old behaviour is restored.I think we should fix it and mb. change default value.
The text was updated successfully, but these errors were encountered: