1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
|
---
author: yyoncho
template: comment.html
root_file: docs/manual-language-docs/lsp-rust-analyzer.md
---
## Server note
NOTE: If you are using `rustic-mode`, you have to change `rustic-lsp-server` instead of `lsp-rust-server`, since it also supports eglot as a lightweight alternative to lsp-mode.
- `lsp-rust-server` Choose LSP server (default is rust-analyzer)
- `lsp-rust-switch-server` Switch priorities of lsp servers
## rust-analyzer
### Commands
#### `lsp-rust-analyzer-syntax-tree`
Display syntax tree for current buffer
#### `lsp-rust-analyzer-status`
Display status information for rust-analyzer
#### `lsp-rust-analyzer-join-lines`
Join selected lines into one, smartly fixing up whitespace and trailing commas
before:
after:
### inlay-hints
`lsp-inlay-hints-mode` enables displaying of inlay hints
Additionally, `lsp-inlay-hint-enable` must be set to `t` in order for inlay hints to render.
NOTE: the inlay hints interact badly with the lsp-ui sideline, because it doesn't seem to consider the overlays in its width calculation, which often leads to lines wrapping around.
### Macro expansion
`lsp-rust-analyzer-expand-macro` expand macro call at point recursively
Use your own function for displaying macro expansion by customizing `lsp-rust-analyzer-macro-expansion-method`
Formatted and highlighted result with the default function of rustic.
### auto-import
Get a list of possible auto import candidates with `lsp-execute-code-action`
### Snippet insertion/refactor
To support refactorings that require snippet insertion(eg. generating
derive clause etc), make sure that you have enabled `yasnippet` and
`yas-minor-mode`. If you are using `use-package`, you can do something
like this:
``` emacs-lisp
(use-package yasnippet
:ensure t
:hook ((lsp-mode . yas-minor-mode)))
```
### Open Cargo.toml
`lsp-rust-analyzer-open-cargo-toml` opens the Cargo.toml closest to the current file. Calling it with a universal argument will open the Cargo.toml in another window.
Corresponds to [the rust-analyzer LSP extension](https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/dev/lsp-extensions.md#open-cargotoml)
### Open external documentation
`lsp-rust-analyzer-open-external-docs` opens external documentation related to the current position in a browser.
Corresponds to [the rust-analyzer LSP extension](https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/dev/lsp-extensions.md#open-external-documentation)
### Find and execute tests related to current position
`lsp-rust-analyzer-related-tests` find all tests related to the current position, asks for user completion and executes the selected test in a compilation buffer.
Corresponds to [the rust-analyzer LSP extension](https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/dev/lsp-extensions.md#related-tests)
In the example below, first you see that:
+ On the left, the function `check_infer` is defined, on the right another
file is opened with many test functions, some of which call `check_infer`.
With the cursor on `check_infer`, call `lsp-rust-analyzer-related-tests`
and select `infer_pattern_match_slice` with fuzzy matching. The test is
executed on the right with compilation major mode
+ Move the cursor to `fn ellipsize` and attempt to find related tests to no
avail. Confirm that the function is indeed untested by using swiper and
finding one place in the file, where the function is called
### Caveats
- Rust Analyzer does not support disabling snippets - https://github.com/rust-analyzer/rust-analyzer/issues/2518
### extract signature
This [unmerged PR](https://github.com/emacs-lsp/lsp-mode/pull/1740) contains an example method that allows
modifying the signature that is displayed by eldoc.
|
