You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I use nix develop '.#rust' -c zsh and open my editor (Neovim), the LSP integration with rust-analyzer works flawlessly (diagnostics from clippy, completions, ...). ✅
If I instead create an .envrc with use flake ${HOME}/myflake#rust, code completions do not trigger in rust-analyzer, although the exact same Nix store directory for Rust tools is present in my PATH in both cases. ❌
This can be replicated in any Cargo project, such as the one bootstrapped by cargo init.
Simply illustated:
nix develop
nix direnv (no LSP completions)
The only noticeable difference from the LSP progress message is that, in the nix-direnv case, progress stops at:
rust-analyzer [Roots Scanned] 15/15
Whereas while using nix develop it continues after that point with:
I haven't noticed any issue in any similar setup, using devShells for Go, Nix and Bash mainly.
I intend to investigate further the differences between the two environment (nix develop vs nix-direnv), but wanted to create an issue anyway with the observed symptoms.
The text was updated successfully, but these errors were encountered:
nix-direnv 3.0.6
I use the following Flake to describe a standard development environment for Rust:
flake.nix
If I use
nix develop '.#rust' -c zsh
and open my editor (Neovim), the LSP integration withrust-analyzer
works flawlessly (diagnostics from clippy, completions, ...). ✅If I instead create an
.envrc
withuse flake ${HOME}/myflake#rust
, code completions do not trigger inrust-analyzer
, although the exact same Nix store directory for Rust tools is present in myPATH
in both cases. ❌This can be replicated in any Cargo project, such as the one bootstrapped by
cargo init
.Simply illustated:
nix develop
nix direnv (no LSP completions)
The only noticeable difference from the LSP progress message is that, in the
nix-direnv
case, progress stops at:Whereas while using
nix develop
it continues after that point with:I haven't noticed any issue in any similar setup, using devShells for Go, Nix and Bash mainly.
I intend to investigate further the differences between the two environment (
nix develop
vsnix-direnv
), but wanted to create an issue anyway with the observed symptoms.The text was updated successfully, but these errors were encountered: