From def3b5d7dd906fd83b24648919f2e86a10afe6a3 Mon Sep 17 00:00:00 2001 From: Mason Shuler Date: Fri, 26 May 2023 16:40:30 -0400 Subject: [PATCH 1/2] Remove outdated rustup installation issue description --- docs/user/manual.adoc | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/docs/user/manual.adoc b/docs/user/manual.adoc index 419f7bac810..babf305794d 100644 --- a/docs/user/manual.adoc +++ b/docs/user/manual.adoc @@ -181,19 +181,6 @@ On Unix, running the editor from a shell or changing the `.desktop` file to set $ rustup component add rust-analyzer ---- -However, in contrast to `component add clippy` or `component add rustfmt`, this does not actually place a `rust-analyzer` binary in `~/.cargo/bin`, see https://github.com/rust-lang/rustup/issues/2411[this issue]. You can find the path to the binary using: -[source,bash] ----- -$ rustup which --toolchain stable rust-analyzer ----- -You can link to there from `~/.cargo/bin` or configure your editor to use the full path. - -Alternatively you might be able to configure your editor to start `rust-analyzer` using the command: -[source,bash] ----- -$ rustup run stable rust-analyzer ----- - ==== Arch Linux The `rust-analyzer` binary can be installed from the repos or AUR (Arch User Repository): From 05d63eff9caa862f3a66e652cd0b247148c316ab Mon Sep 17 00:00:00 2001 From: Mason Shuler Date: Fri, 26 May 2023 16:41:51 -0400 Subject: [PATCH 2/2] Make rustup heading title match other titles --- docs/user/manual.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user/manual.adoc b/docs/user/manual.adoc index babf305794d..5b9db10b093 100644 --- a/docs/user/manual.adoc +++ b/docs/user/manual.adoc @@ -172,7 +172,7 @@ $ cargo xtask install --server If your editor can't find the binary even though the binary is on your `$PATH`, the likely explanation is that it doesn't see the same `$PATH` as the shell, see https://github.com/rust-lang/rust-analyzer/issues/1811[this issue]. On Unix, running the editor from a shell or changing the `.desktop` file to set the environment should help. -==== `rustup` +==== rustup `rust-analyzer` is available in `rustup`: