You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 8, 2020. It is now read-only.
As per #289, #315 introduces a new configuration parameter, "rust.shell.kind.windows" which can be used to specify what kind of terminal is used.
If the user uses WSL and Cargo commands are executed through rustup, then "rust.rustup.toolchain" will be used as a toolchain which rustup will be invoked with.
The problem is that the extension allows to choose only toolchains installed on Windows (not WSL) and hence rustup will be invoked with some not installed toolchain.
The workaround is to install the toolchain on Windows which will be used in WSL.
An example: nightly-x86_64-unknown-linux-gnu
The motivation is described in #315
The text was updated successfully, but these errors were encountered:
As per #289, #315 introduces a new configuration parameter,
"rust.shell.kind.windows"
which can be used to specify what kind of terminal is used.If the user uses WSL and Cargo commands are executed through rustup, then
"rust.rustup.toolchain"
will be used as a toolchain which rustup will be invoked with.The problem is that the extension allows to choose only toolchains installed on Windows (not WSL) and hence rustup will be invoked with some not installed toolchain.
The workaround is to install the toolchain on Windows which will be used in WSL.
An example: nightly-x86_64-unknown-linux-gnu
The motivation is described in #315
The text was updated successfully, but these errors were encountered: