ALE runs the linter in the original path that vim opened with, not the project directory. #3874
Answered
by
hsanson
LollipopFt
asked this question in
Q&A - Ask for help with problems
-
Command History:
(executable check - success) cargo
(finished - exit code 0) 'cmd /s/c "cargo --version"'
<<<OUTPUT STARTS>>>
cargo 1.54.0 (5ae8d74b3 2021-06-22)
<<<OUTPUT ENDS>>>
(finished - exit code 101) 'cmd /s/c "cargo clippy --frozen --message-format=json -q"'
<<<OUTPUT STARTS>>>
error: could not find `Cargo.toml` in `C:\Users\lollipopft` or any parent directory
<<<OUTPUT ENDS>>>
(finished - exit code 101) 'cmd /s/c "cargo clippy --frozen --message-format=json -q"'
<<<OUTPUT STARTS>>>
error: could not find `Cargo.toml` in `C:\Users\lollipopft` or any parent directory
<<<OUTPUT ENDS>>>
(finished - exit code 101) 'cmd /s/c "cargo clippy --frozen --message-format=json -q"'
<<<OUTPUT STARTS>>>
error: could not find `Cargo.toml` in `C:\Users\lollipopft` or any parent directory
<<<OUTPUT ENDS>>>is there a way to fix this? |
Beta Was this translation helpful? Give feedback.
Answered by
hsanson
Aug 19, 2021
Replies: 1 comment
-
|
What linter you are trying to use? Posting the whole ALEInfo could help figure out things better. Depending on the project structure and linter, ALE may not be able to determine the root of a project and require help from the user. See |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
LollipopFt
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What linter you are trying to use? Posting the whole ALEInfo could help figure out things better.
Depending on the project structure and linter, ALE may not be able to determine the root of a project and require help from the user. See
:h ale-root.