aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorveetaha <[email protected]>2020-04-02 09:23:56 +0100
committerveetaha <[email protected]>2020-04-02 09:23:56 +0100
commitdd5e4d4870b4e59bc82d285c481bb6971d016912 (patch)
tree672f5ebda7447c06ff28556515e41b13cef261e1 /docs
parent036a8aee2af960428218cecd68ea2ea1813ab7f6 (diff)
vscode: move docks about syntax tree to dev/README.md
Diffstat (limited to 'docs')
-rw-r--r--docs/dev/README.md10
-rw-r--r--docs/user/features.md10
2 files changed, 10 insertions, 10 deletions
diff --git a/docs/dev/README.md b/docs/dev/README.md
index 8d7e18010..f230dc1db 100644
--- a/docs/dev/README.md
+++ b/docs/dev/README.md
@@ -155,6 +155,16 @@ There's also two VS Code commands which might be of interest:
155 155
156* `Rust Analyzer: Syntax Tree` shows syntax tree of the current file/selection. 156* `Rust Analyzer: Syntax Tree` shows syntax tree of the current file/selection.
157 157
158 You can hover over syntax nodes in the opened text file to see the appropriate
159 rust code that it refers to and the rust editor will also highlight the proper
160 text range.
161
162 If you press <kbd>Ctrl</kbd> (i.e. trigger goto definition) in the inspected
163 Rust source file the syntax tree read-only editor should scroll to and select the
164 appropriate syntax node token.
165
166 ![demo](https://user-images.githubusercontent.com/36276403/78225773-6636a480-74d3-11ea-9d9f-1c9d42da03b0.png)
167
158# Profiling 168# Profiling
159 169
160We have a built-in hierarchical profiler, you can enable it by using `RA_PROFILE` env-var: 170We have a built-in hierarchical profiler, you can enable it by using `RA_PROFILE` env-var:
diff --git a/docs/user/features.md b/docs/user/features.md
index 4cba66529..56d2969fd 100644
--- a/docs/user/features.md
+++ b/docs/user/features.md
@@ -81,16 +81,6 @@ Join selected lines into one, smartly fixing up whitespace and trailing commas.
81Shows the parse tree of the current file. It exists mostly for debugging 81Shows the parse tree of the current file. It exists mostly for debugging
82rust-analyzer itself. 82rust-analyzer itself.
83 83
84You can hover over syntax nodes in the opened text file to see the appropriate
85rust code that it refers to and the rust editor will also highlight the proper
86text range.
87
88If you press <kbd>Ctrl</kbd> (i.e. trigger goto definition) in the inspected
89Rust source file the syntax tree readonly editor should scroll to and select the
90appropriate syntax node token.
91
92<img src="https://user-images.githubusercontent.com/36276403/78043783-7425e180-737c-11ea-8653-b02b773c5aa1.png" alt="demo" height="200px" >
93
94#### Expand Macro Recursively 84#### Expand Macro Recursively
95 85
96Shows the full macro expansion of the macro at current cursor. 86Shows the full macro expansion of the macro at current cursor.