rust-lang / rust-lang/rust-analyzer
option to specify path to cargo executable
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
in my project, cargo is installed to a python virtual environment using https://github.com/konstin/rustup-pypi. this works with the language server thanks to the rust-analyzer.server.path setting:
// .vscode/settings.json
{
"rust-analyzer.server.path": ".venv/bin/rust-analyzer"
}
however there doesn't seem to be a setting to specify the path to the cargo executable, so i can't use the run/debug buttons in my main.rs:
2025-11-24 23:17:32.911 [error] Cargo invocation has failed: Error: could not launch cargo: Error: spawn cargo ENOENT
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the .vscode/settings.json example and the run/debug entry points used for main.rs, then trace how the Cargo invocation is configured. Add a way to provide the cargo executable path, and verify that the run/debug buttons use the configured executable instead of failing with spawn cargo ENOENT.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100