-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Support --target-dir
with rust-analyzer
#4557
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
Seems related to this rust-lang/rust-analyzer#6007 Some notable take-aways from that thread:
In ALE, the configuration would look something like this:
Give this a try and let us know. |
Ah, I missed the extra layer there. I had tried: let g:ale_rust_analyzer_config = {
\ 'rust-analyzer.server.extraEnv': {
\ 'CARGO_TARGET_DIR': 'target/analyzer'
\ }
\} |
That works, thanks. I'll see if I can improve the docs for that instead of just being "Dictionary with configuration settings for rust-analyzer.". |
mathstuf
added a commit
to mathstuf/vim-ale
that referenced
this issue
Jul 20, 2023
hsanson
pushed a commit
that referenced
this issue
Jul 24, 2023
mnikulin
pushed a commit
to mnikulin/ale
that referenced
this issue
Nov 12, 2023
cyyever
pushed a commit
to cyyever/ale
that referenced
this issue
Mar 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
rust-analyzer
currently locks the default build directory. It'd be nice to be able to use a different directory to avoidcargo
commands blockingrust-analyzer
and vice versa. I've tried adding things tog:ale_rust_analyzer_config
, but I wasn't able to plumb through the--target-dir
setting.The text was updated successfully, but these errors were encountered: