Thanks for figuring out why VS code doesn’t just do the right thing for terminal hyperlinks (at least optionally, if within workspace etc.) Not that it helps, but good to know!
As for the option, I had been going over rust-analyzer --help to find it and ask VS code to pass it. Instead it’s there as an option to set directly in VS code – even labelled right. Just the explanation of true is rather wishy-washy. Instead of “a subdirectory of the existing target directory”, leaving us guessing, it should name <WORKDIR>/target/rust-analyzer or <TARGETDIR>/rust-analyzer!
This is a life-saver. Thank you so much. I just wonder why setting it to true is not the default! I always took care to pass the option to cargo so I could get on with life, without VS code blocking me. At least the trade-off with disk-space should be prominently explained, so everybody can choose easily!