Mirrors/rust-analyzer
2
0
Fork 0
mirror of https://github.com/rust-lang/rust-analyzer synced 2024-12-27 05:23:24 +00:00
Code Issues Projects Releases Packages Wiki Activity

xtask does not need to be installed

Browse source 
because it's contained in the dart-analyzer repo.
This commit is contained in:
Günter Zöchbauer 2020-04-26 17:08:15 +02:00 committed by GitHub
parent 49d494c033
commit 482e912fa0
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
docs/user/readme.adoc
View file

@ -94,8 +94,7 @@ $ git clone https://github.com/rust-analyzer/rust-analyzer.git && cd rust-analyz
$ cargo xtask install $ cargo xtask install
---- ----
You'll need Cargo, xtask, nodejs and npm for this. You'll need Cargo, nodejs and npm for this.
Cargo-xtask can be found at https://github.com/matklad/cargo-xtask
Note that installing via `xtask install` does not work for VS Code Remote, instead you'll need to install the `.vsix` manually. Note that installing via `xtask install` does not work for VS Code Remote, instead you'll need to install the `.vsix` manually.
@ -130,8 +129,6 @@ $ git clone https://github.com/rust-analyzer/rust-analyzer.git && cd rust-analyz
$ cargo xtask install --server $ cargo xtask install --server
---- ----
Cargo-xtask can be found at https://github.com/matklad/cargo-xtask
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-analyzer/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. 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-analyzer/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.
==== Arch Linux ==== Arch Linux