Mirrors/rust-analyzer
2
0
Fork 0
mirror of https://github.com/rust-lang/rust-analyzer synced 2025-01-13 13:48:50 +00:00
Code Issues Projects Releases Packages Wiki Activity

Merge #4536

Browse source 
4536: Fix names of launch configuration in dev docs r=kjeremy a=kuy

Follows renaming of launch configurations in 80a42a0628

Co-authored-by: Yuki Kodama <endflow.net@gmail.com>
This commit is contained in:
bors[bot] 2020-05-20 19:04:02 +00:00 committed by GitHub
commit 3dfc461f1e
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/dev/README.md
View file

@ -74,7 +74,7 @@ relevant test and execute it (VS Code includes an action for running a single
test). test).
However, launching a VS Code instance with locally build language server is However, launching a VS Code instance with locally build language server is
possible. There's **"Run Extension (Dev Server)"** launch configuration for this. possible. There's **"Run Extension (Debug Build)"** launch configuration for this.
In general, I use one of the following workflows for fixing bugs and In general, I use one of the following workflows for fixing bugs and
implementing features. implementing features.
@ -86,7 +86,7 @@ then just do printf-driven development/debugging. As a sanity check after I'm
done, I use `cargo xtask install --server` and **Reload Window** action in VS done, I use `cargo xtask install --server` and **Reload Window** action in VS
Code to sanity check that the thing works as I expect. Code to sanity check that the thing works as I expect.
If the problem concerns only the VS Code extension, I use **Run Extension** If the problem concerns only the VS Code extension, I use **Run Installed Extension**
launch configuration from `launch.json`. Notably, this uses the usual launch configuration from `launch.json`. Notably, this uses the usual
`rust-analyzer` binary from `PATH`. For this it is important to have the following `rust-analyzer` binary from `PATH`. For this it is important to have the following
in `setting.json` file: in `setting.json` file:

6
docs/dev/debugging.md
View file

@ -22,8 +22,8 @@ where **only** the `rust-analyzer` extension being debugged is enabled.
## Debug TypeScript VSCode extension ## Debug TypeScript VSCode extension
- `Run Extension` - runs the extension with the globally installed `rust-analyzer` binary. - `Run Installed Extension` - runs the extension with the globally installed `rust-analyzer` binary.
- `Run Extension (Dev Server)` - runs extension with the locally built LSP server (`target/debug/rust-analyzer`). - `Run Extension (Debug Build)` - runs extension with the locally built LSP server (`target/debug/rust-analyzer`).
TypeScript debugging is configured to watch your source edits and recompile. TypeScript debugging is configured to watch your source edits and recompile.
To apply changes to an already running debug process, press <kbd>Ctrl+Shift+P</kbd> and run the following command in your `[Extension Development Host]` To apply changes to an already running debug process, press <kbd>Ctrl+Shift+P</kbd> and run the following command in your `[Extension Development Host]`
@ -47,7 +47,7 @@ To apply changes to an already running debug process, press <kbd>Ctrl+Shift+P</k
debug = 2 debug = 2
``` ```
- Select `Run Extension (Dev Server)` to run your locally built `target/debug/rust-analyzer`. - Select `Run Extension (Debug Build)` to run your locally built `target/debug/rust-analyzer`.
- In the original VSCode window once again select the `Attach To Server` debug configuration. - In the original VSCode window once again select the `Attach To Server` debug configuration.