Closed stradicat closed 7 months ago
Enabling lsp-io-mode
and reloading the Rust file shows the following warning:
Suspicious state from syntax checker rustic-clippy: Flycheck checker rustic-clippy returned 101, but its output contained no errors: error: could not find 'Cargo.toml' in '/Users/my_user/Documents/project_directory' or any parent directory
This hasn't happened before when opening Rust files in their own directories.
After the last lsp-mode
update, it seems to be working again.
Closing.
Description :octocat:
LSP + Rust layer: no syntax check,
rust-analyzer
loaded but inactive. Runninglsp-rust-analyzer-run
ends up in error:When trying to switch the Rust backend with
SPC m s s
, the following warning shows up right atSPC m s
:Other LSP-enabled layers such as
javascript
,c-c++
andgo
are working without problems after this week's updates.Could this be related ot the
helm-descbinds
vswhich-key
problem arised during the past few days?Reproduction guide :beetle:
rust
andlsp
layers enabledlsp-install-server
, then chooserust-analyzer
.rs
Rust project file or create some short Rust code, such asprintln!("Testing");
. Begin typingprintln!
, wait for autocompletion to kick-in.Observed behaviour: :eyes: :broken_heart:
Expected behaviour: :heart: :smile:
System Info :computer: