-
Notifications
You must be signed in to change notification settings - Fork 1.5k
TSLint exits with error code 127 (Command not found?) #1666
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
Comments
Could you create an example project on GitHub which reproduces the issue? I won't be able to reproduce this issue on my machine. |
I tried on DomesticApp/ionic-test-doubles and I managed to reproduce the same error:
|
I'm going to try deleting all the plugins and reinstalling them. |
Reinstalling everything didn't work. |
I tried cloning that project and checking the files inside it with tslint installed to |
Should be caused by something wrong in my settings? |
I'm not sure myself. |
I managed to get this error from the job running the linter:
Its because I'm using nvm... |
Aha, that makes more sense. Maybe there's a way ALE could detect if |
Setting up
|
Okay, I guess you must have needed some kind of environment variable set in there. |
Information
VIM version
Operating System:
Linux 4.16.13-2-ARCH GNU/Linux
:ALEInfo
What went wrong
Linter stops working and as you can tell from
ALEInfo
the command exits with 127 status code which seems to beCommand not found
error in bash.When I try to run the entire command from bash it works as expected, and everything is installed
Reproducing the bug
The text was updated successfully, but these errors were encountered: