-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
What about the tools not reading from stdin? #28
Comments
The best tools accept stdin input. For the tools that don't there is a Bash wrapper script which writes the output to a temporary file which can be used. Have a look at the Haskell GHC linter. That one uses the wrapper script at the moment. |
The wrapper works as expected but it is not cross-platform. Anyway, I'll add some linters using the script meanwhile a better approach. |
I might see if I can get a wrapper script written for Windows using Batch hacks, and then I would be able to support all of Windows, Linux, and Mac OSX. That would make me happy enough. |
That would make everyone happy |
How can I find this wrapper script? |
I would like to add many linters that unfortunately do not read from stdin (csslint, sass-lint, vint...). Is there any plans or strategy to handle those kind of tools in ale?
In fact, I can easily add them to validator but I prefer to use a solution full vimscript as your plugin.
The text was updated successfully, but these errors were encountered: