ALE fails to lint - says "No active LSPs" #3629
Replies: 8 comments 2 replies
-
OMG: I tried a number of things over a period of serval hours (ALE is fundamental to my work flow) none of which seemed to help:
This morning, I tried installing an LSP, just for grins: typescript-language-server. This didn't help, but when I uninstalled it and tried ALEInfo again, now it's working! |
Beta Was this translation helpful? Give feedback.
-
Would love to have some understanding of what happened here, but I'm overjoyed to have found a solution. |
Beta Was this translation helpful? Give feedback.
-
Well... just happened to me again. Only thing I can think of is that I installed What is keeping ALE from actually running the required commands? Anything I can do to help debug? And now its working on most files but still failing on the src/App.js file... weird. |
Beta Was this translation helpful? Give feedback.
-
Look at the |
Beta Was this translation helpful? Give feedback.
-
Thanks, @w0rp -- In those cases where it fails, there is literally no
|
Beta Was this translation helpful? Give feedback.
-
And yes, |
Beta Was this translation helpful? Give feedback.
-
If it's not even checking if any executables that exist, I have no idea. I use ALE every day at work with ESLint, TypesScript, and Pyright, so it's not something wrong with ALE. You'll have to eliminate one issue at a time like searching for any copies of ALE in runtimepath, removing them all and reinstalling the plugin, looking for anything in your Vim settings that might cause an issue. It could be anything. |
Beta Was this translation helpful? Give feedback.
-
Yeah; really weird.. it seems to come and go. Thanks; I’ll try looking for multiple copies of ALE and also reinstalling.
An d yes, I use it every day on multiple projects, have for years, and love it. Just wish I could figure out what’s going on.
Cheers…jon
Stay safe; be well.
… On Feb 14, 2021, at 3:37 PM, w0rp ***@***.***> wrote:
If it's not even checking if any executables that exist, I have no idea. I use ALE every day at work with ESLint, TypesScript, and Pyright, so it's not something wrong with ALE. You'll have to eliminate one issue at a time like searching for any copies of ALE in runtimepath, removing them all and reinstalling the plugin, looking for anything in your Vim settings that might cause an issue. It could be anything.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub <#3542 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAADZUPVX723JSADR5O56DS7BNCLANCNFSM4WFJNZ2Q>.
|
Beta Was this translation helpful? Give feedback.
-
Information
VIM version
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Dec 6 2020 16:07:31)
macOS version
Operating System:
MacOS Cataling 10.15.7 (19H2)
What went wrong
I've been using ALE for several years now and love it. Recently something broke and now ALE doesn't work in my code.
No active LSPs
npx eslint -f unix --stdin --stdin-filename src/App.js < src/App.js
produces the expected output:npx eslint --version
showsV7.14.0
npx stylelint --version
shows13.8.0
.javascript.jsx
as the filetype for both.js
and.jsx
filesI've tried
:set ft=javascript
but that doesn't fix the problemReproducing the bug
This happens with any javascript file that I edit.
:ALEInfo
NOTE: No command history
Beta Was this translation helpful? Give feedback.
All reactions