diff options
| author | wtj <zhangwt1997@gmail.com> | 2023-04-27 12:21:23 +0800 |
|---|---|---|
| committer | wtj <zhangwt1997@gmail.com> | 2023-04-28 18:49:05 +0800 |
| commit | c533ac357391e7f9d5c7a3eea09a5e2dedc89c5c (patch) | |
| tree | 06ddb95ad614ff884b008c3f925410128575b590 | |
| parent | 237ffa3997250b8569ced477a5072310eb48c847 (diff) | |
| download | rust-c533ac357391e7f9d5c7a3eea09a5e2dedc89c5c.tar.gz rust-c533ac357391e7f9d5c7a3eea09a5e2dedc89c5c.zip | |
minor: fix typos
| -rw-r--r-- | crates/hir/src/lib.rs | 2 | ||||
| -rw-r--r-- | docs/user/manual.adoc | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/crates/hir/src/lib.rs b/crates/hir/src/lib.rs index 7e141a9e364..a65cbf8ff14 100644 --- a/crates/hir/src/lib.rs +++ b/crates/hir/src/lib.rs @@ -6,7 +6,7 @@ //! applied. So, the relation between syntax and HIR is many-to-one. //! //! HIR is the public API of the all of the compiler logic above syntax trees. -//! It is written in "OO" style. Each type is self contained (as in, it knows it's +//! It is written in "OO" style. Each type is self contained (as in, it knows its //! parents and full context). It should be "clean code". //! //! `hir_*` crates are the implementation of the compiler logic. diff --git a/docs/user/manual.adoc b/docs/user/manual.adoc index cb96feeb5e5..419f7bac810 100644 --- a/docs/user/manual.adoc +++ b/docs/user/manual.adoc @@ -589,7 +589,7 @@ Try **rust-analyzer: Show RA Version** in VS Code (using **Command Palette** fea If the date is more than a week ago, it's better to update rust-analyzer version. The next thing to check would be panic messages in rust-analyzer's log. -Log messages are printed to stderr, in VS Code you can see then in the `Output > Rust Analyzer Language Server` tab of the panel. +Log messages are printed to stderr, in VS Code you can see them in the `Output > Rust Analyzer Language Server` tab of the panel. To see more logs, set the `RA_LOG=info` environment variable, this can be done either by setting the environment variable manually or by using `rust-analyzer.server.extraEnv`, note that both of these approaches require the server to be restarted. To fully capture LSP messages between the editor and the server, set `"rust-analyzer.trace.server": "verbose"` config and check |