diff options
| author | Günter Zöchbauer <[email protected]> | 2020-04-26 16:08:15 +0100 |
|---|---|---|
| committer | GitHub <[email protected]> | 2020-04-26 16:08:15 +0100 |
| commit | 482e912fa0b1df03c6ad99c1d92a894889811e00 (patch) | |
| tree | 4720820a45c4c8cf0c1f5b3644e3e96575069aeb | |
| parent | 49d494c03307cff75057a856eadc5ebb5ff1ea9d (diff) | |
xtask does not need to be installed
because it's contained in the dart-analyzer repo.
| -rw-r--r-- | docs/user/readme.adoc | 5 |
1 files changed, 1 insertions, 4 deletions
diff --git a/docs/user/readme.adoc b/docs/user/readme.adoc index 5e4ce3055..c6c0f3ed8 100644 --- a/docs/user/readme.adoc +++ b/docs/user/readme.adoc | |||
| @@ -94,8 +94,7 @@ $ git clone https://github.com/rust-analyzer/rust-analyzer.git && cd rust-analyz | |||
| 94 | $ cargo xtask install | 94 | $ cargo xtask install |
| 95 | ---- | 95 | ---- |
| 96 | 96 | ||
| 97 | You'll need Cargo, xtask, nodejs and npm for this. | 97 | You'll need Cargo, nodejs and npm for this. |
| 98 | Cargo-xtask can be found at https://github.com/matklad/cargo-xtask | ||
| 99 | 98 | ||
| 100 | Note that installing via `xtask install` does not work for VS Code Remote, instead you'll need to install the `.vsix` manually. | 99 | Note that installing via `xtask install` does not work for VS Code Remote, instead you'll need to install the `.vsix` manually. |
| 101 | 100 | ||
| @@ -130,8 +129,6 @@ $ git clone https://github.com/rust-analyzer/rust-analyzer.git && cd rust-analyz | |||
| 130 | $ cargo xtask install --server | 129 | $ cargo xtask install --server |
| 131 | ---- | 130 | ---- |
| 132 | 131 | ||
| 133 | Cargo-xtask can be found at https://github.com/matklad/cargo-xtask | ||
| 134 | |||
| 135 | 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. | 132 | 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. |
| 136 | 133 | ||
| 137 | ==== Arch Linux | 134 | ==== Arch Linux |