From 43619ea87fee21d1a8134f56ea72c1b53ddb87ae Mon Sep 17 00:00:00 2001 From: Jorge Aparicio Date: Mon, 13 Jul 2020 15:54:00 +0000 Subject: [PATCH] Update embedded-workshop-book/src/troubleshoot-rust-analyzer.md Co-authored-by: Jonas Schievink --- embedded-workshop-book/src/troubleshoot-rust-analyzer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/embedded-workshop-book/src/troubleshoot-rust-analyzer.md b/embedded-workshop-book/src/troubleshoot-rust-analyzer.md index 5a6593b..0ec3ccc 100644 --- a/embedded-workshop-book/src/troubleshoot-rust-analyzer.md +++ b/embedded-workshop-book/src/troubleshoot-rust-analyzer.md @@ -4,6 +4,6 @@ If Rust-Analyzer is not analyzing your code, that is you get no type annotations - check that you have a single folder open in VS code; this is different from a single-folder VS code workspace. First close all the currently open folders then open a single folder using the 'File > Open Folder' menu. The open folder should be the `beginner/apps` folder for the beginner workshop or the `advanced/firmware` folder for the advanced workshop. -- use the latest version of the Rust-Analyzer plugin. If you get a prompt to update the Rust-Analyzer extension hen you start VS code accept it. You may also get a prompt about updating the Rust-Analayzer binary; accept that one too. The extension should restart automatically after the update. If it doesn't then close and re-open VS code. +- use the latest version of the Rust-Analyzer plugin. If you get a prompt to update the Rust-Analyzer extension when you start VS code accept it. You may also get a prompt about updating the Rust-Analayzer binary; accept that one too. The extension should restart automatically after the update. If it doesn't then close and re-open VS code. - You may need to wait a little while Rust-Analyzer analyzes all the crates in the dependency graph. Then you may need to modify and save the currently open file to force Rust-Analyzer to analyze it.