Unnamed repository; edit this file 'description' to name the repository.
Spelling nits
| -rw-r--r-- | crates/ide_completion/src/completions/attribute.rs | 2 | ||||
| -rw-r--r-- | docs/user/manual.adoc | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/crates/ide_completion/src/completions/attribute.rs b/crates/ide_completion/src/completions/attribute.rs index d642c8bc4d..8222d3cbf4 100644 --- a/crates/ide_completion/src/completions/attribute.rs +++ b/crates/ide_completion/src/completions/attribute.rs @@ -2,7 +2,7 @@ //! //! This module uses a bit of static metadata to provide completions //! for built-in attributes. -//! Non-builtin attribute(excluding derives attributes) completions are done in [`super::unqualified_path`]. +//! Non-built-in attribute (excluding derives attributes) completions are done in [`super::unqualified_path`]. use ide_db::{ helpers::{ diff --git a/docs/user/manual.adoc b/docs/user/manual.adoc index 1db6cb5cd4..4fbe2379c3 100644 --- a/docs/user/manual.adoc +++ b/docs/user/manual.adoc @@ -445,7 +445,7 @@ 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. -To see more logs, set `RA_LOG=info` environmental variable. +To see more logs, set the `RA_LOG=info` environment variable. To fully capture LSP messages between the editor and the server, set `"rust-analyzer.trace.server": "verbose"` config and check `Output > Rust Analyzer Language Server Trace`. @@ -624,7 +624,7 @@ Relative paths are interpreted relative to `rust-project.json` file location or See https://github.com/rust-analyzer/rust-project.json-example for a small example. -You can set `RA_LOG` environmental variable to `rust_analyzer=info` to inspect how rust-analyzer handles config and project loading. +You can set the `RA_LOG` environment variable to `rust_analyzer=info` to inspect how rust-analyzer handles config and project loading. Note that calls to `cargo check` are disabled when using `rust-project.json` by default, so compilation errors and warnings will no longer be sent to your LSP client. To enable these compilation errors you will need to specify explicitly what command rust-analyzer should run to perform the checks using the `checkOnSave.overrideCommand` configuration. As an example, the following configuration explicitly sets `cargo check` as the `checkOnSave` command. |