every time I used gd to inspect some definitions, my neovim takes me to the exact location where the symbols are defined--which is what i want; however, my rust analyzer started analyzing the entire library crate and creates a pretty big target directory inside of the library. Is there a way for me to stop this in neovim? Before I used neovim, I used vscode, and I never had a problem like this while using it.
#is there a way to stop neovim rust analyzer to create a target directory inside of library crates?
crimson holly
void magnet
vscode doesnt do that? it maybe because some specific config in there that routes it to somewhere else.
thats what i currently have with mine (in helix).
you can set rust-analyzer.cargo.extraEnv
and put in CARGO_TARGET_DIR with directory to somewhere you like
crimson holly
vscode doesnt do that? it maybe because some specific config in there that route...
hmm if vscode does that too then i think im fine with leaving everything as is
i thought if vscode doesnt need to create a target directory in the library crates then there must be a to prevent neovim from doing just that