This repository has been archived by the owner on Nov 18, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 168
Cargo not found in "Run Test" #620
Comments
Looks like its the problem from VSCode insider, recent update fix this issue. |
I have the same problem. vscode
|
I have solved this proplem. It is obviously that
add function createShellExecution(execution) {
const { binary, command, args, cwd, env } = execution;
// const cmdLine = `${command || binary} ${args.join(' ')}`;
const cmdLine = `source $HOME/.cargo/env; ${command || binary} ${args.join(' ')}`;
return new vscode_1.ShellExecution(cmdLine, { cwd, env });
} But I think there will be some better solution than mine. Maybe change the |
I found another issue. I have set vscode setting.json with this option "terminal.integrated.inheritEnv": false, // delete it or set to `true` delete it or set to |
matklad
pushed a commit
to matklad/vscode-rust
that referenced
this issue
Jul 13, 2020
738: Implement lens for impls and support resolving lenses. r=matklad a=kjeremy Closes rust-lang#620 Co-authored-by: Jeremy Kolb <kjeremy@gmail.com> Co-authored-by: kjeremy <kjeremy@gmail.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am using:
rls:
1.37.0 (124483d 2019-07-01)
rls-vscode:
0.6.1
VS Code:
1.36.0-insider
OS:
Linux 4.18.0-22-generic #23~18.04.1-Ubuntu
(Ubuntu 18.04 LTS) (using vscode remote, local OS:18.6.0 Darwin
(macOS Mojave 10.14.5))I am having the full absolute path in
rust-client.rlsPath
andrust-client.rustupPath
.When using the
Run Test
feature, the terminal cannot find cargo. Its probably related to the $PATH used by rls/rls-vscode.While I can use the reused VSCode terminal to do the same command without error.
The text was updated successfully, but these errors were encountered: