Closed Kazark closed 7 years ago
I think I've actually solved this now. Looks like elm-make
only respects /dev/null
, even on Windows. The person who wrote this linter maybe did not test it on Windows, and wrote the code in the way you would expect to be solid by using NUL
on Windows. However it seems elm-make
is not actually making use of /dev/null
but rather using it as a form of flag. I will submit a PR.
Fixed in #981
I'm not surprised by that /dev/null
behaviour. The same thing happend with one of the Go tools too.
I was going to cherry-pick this for a 1.5.x release, but the bug was only present on master
. Thank you for fixing this!
@w0rp Sure! Thanks for ALE!
Problem
I just installed ALE, replacing Syntastic, to use with Elm[-vim]. When I load an Vim buffer, I get exactly one complaint, at the top of the file:
My Solution
I was able to fix this by commenting out one line:
After that, I am able to get errors like I would expect, but once I fix them all I get another top-level error saying
For which I changed another line, resulting in:
Detailed Info
I am on Elm 0.18.0:
I'm running Windows 7. Vim info:
Output of
:ALEInfoToClipboard
:Reproducing the problem myself on the command-line: