-
Notifications
You must be signed in to change notification settings - Fork 162
rls-vscode doesn't work with multi-root vscode workspaces #194
Comments
On my laptop, checking the RLS logs in VSCode gives me: note: rustc 1.23.0-nightly (5f44c653c 2017-11-24) running on x86_64-apple-darwin
thread 'rustc' panicked at 'Could not deserialize save-analysis config: MissingFieldError("reachable_only")', src/libcore/result.rs:906:4
note: Run with `RUST_BACKTRACE=1` for a backtrace. I don't know if this is related to workspaces, but this is very likely related to rust-lang/rust#46244. |
@yamafaktory this is not related to workspaces, it should be fixed soon... |
@nrc Thanks a lot for the feedback, I'll wait for it! It's an awesome work you're doing & an awesome tool too! |
The official lsp client we're using already supports workspace extension (https://github.com/Microsoft/vscode-languageserver-node/blob/master/protocol/src/protocol.workspaceFolders.proposed.md), so this needs only toggling on from the client side. |
With a workspace like this:
(i.e. containing several folders that are not rust related and one that is a rust project) the extensions will not work because the root of the rust project is not correct. Is it possible, in this case, to start RLS on the rust folder of the workspace ? |
In addition, if a workspace contains several unrelated rust projects, is it possible to start one RLS by rust folder ? |
Fixed. |
https://code.visualstudio.com/docs/editor/multi-root-workspaces
No autocomplete / no red-squigglies, etc
RLS shows that it has loaded and is Done, but it everything functions as though rls-vscode isn't even installed.
The text was updated successfully, but these errors were encountered: