aboutsummaryrefslogtreecommitdiff
path: root/docs/user
diff options
context:
space:
mode:
authorbors[bot] <26634292+bors[bot]@users.noreply.github.com>2021-05-17 15:41:56 +0100
committerGitHub <[email protected]>2021-05-17 15:41:56 +0100
commitf9d4a9eaee6f86d9bd60cf6d18ec744b56696135 (patch)
tree31c5c36a446ca3cd123309ac85dc39e0e23cdc74 /docs/user
parentfa02911078cfa1b3d3b9fb2cbbed9d1de98cd88e (diff)
parent7ae3967e5739b786fcd3f7b7b333c73f2c38e8dd (diff)
Merge #8795
8795: Allow semantic tokens for strings to be disabled r=matklad a=djrenren Fixes https://github.com/rust-analyzer/rust-analyzer/issues/7111 Pretty straightforward change, but open to any suggestions if there's a more recommended testing strategy than what I went with. Co-authored-by: John Renner <[email protected]>
Diffstat (limited to 'docs/user')
-rw-r--r--docs/user/generated_config.adoc9
1 files changed, 9 insertions, 0 deletions
diff --git a/docs/user/generated_config.adoc b/docs/user/generated_config.adoc
index f70558200..e2d74e164 100644
--- a/docs/user/generated_config.adoc
+++ b/docs/user/generated_config.adoc
@@ -332,3 +332,12 @@ Additional arguments to `rustfmt`.
332Advanced option, fully override the command rust-analyzer uses for 332Advanced option, fully override the command rust-analyzer uses for
333formatting. 333formatting.
334-- 334--
335[[rust-analyzer.semanticStringTokens]]rust-analyzer.semanticStringTokens (default: `true`)::
336+
337--
338Use semantic tokens for strings.
339
340In some editors (e.g. vscode) semantic tokens override other highlighting grammars.
341By disabling semantic tokens for strings, other grammars can be used to highlight
342their contents.
343--