Unnamed repository; edit this file 'description' to name the repository.
Diffstat (limited to 'docs/book/src/configuration.md')
-rw-r--r--docs/book/src/configuration.md7
1 files changed, 6 insertions, 1 deletions
diff --git a/docs/book/src/configuration.md b/docs/book/src/configuration.md
index fd94a4221a..708eecd435 100644
--- a/docs/book/src/configuration.md
+++ b/docs/book/src/configuration.md
@@ -13,7 +13,7 @@ Vim](./other_editors.md#coc-rust-analyzer) provide `rust-analyzer` specific conf
UIs. Others may require you to know a bit more about the interaction
with `rust-analyzer`.
-For the later category, it might help to know that the initial
+For the latter category, it might help to know that the initial
configuration is specified as a value of the `initializationOptions`
field of the [`InitializeParams` message, in the LSP
protocol](https://microsoft.github.io/language-server-protocol/specifications/specification-current/#initialize).
@@ -46,6 +46,11 @@ To verify which configuration is actually used by `rust-analyzer`, set
config-related messages. Logs should show both the JSON that
`rust-analyzer` sees as well as the updated config.
+(Work in progress:) It is also possible to place configuration in a
+`rust-analyzer.toml` file. It should be located in the project root or in your
+user configuration directory (e.g. `~/.config/rust-analyzer/`). This is a work in
+progress, many configuration options aren't supported yet.
+
This is the list of config options `rust-analyzer` supports:
{{#include configuration_generated.md}}