From f21f52343db942bd39ed6a2bb196d01aaf1f741f Mon Sep 17 00:00:00 2001 From: Keith Pinson Date: Fri, 6 Oct 2017 17:26:50 -0400 Subject: Fix Elm linter for Windows (resolves #980) 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. Ironically this seems to be what is already described in the comments; I added some clarification. --- ale_linters/elm/make.vim | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ale_linters/elm/make.vim b/ale_linters/elm/make.vim index 4038e3b4..3783b5e3 100644 --- a/ale_linters/elm/make.vim +++ b/ale_linters/elm/make.vim @@ -71,11 +71,11 @@ function! ale_linters#elm#make#GetCommand(buffer) abort " The elm-make compiler, at the time of this writing, uses '/dev/null' as " a sort of flag to tell the compiler not to generate an output file, - " which is why this is hard coded here. + " which is why this is hard coded here. It does not use NUL on Windows. " Source: https://github.com/elm-lang/elm-make/blob/master/src/Flags.hs let l:elm_cmd = ale#Escape(l:elm_exe) \ . ' --report=json' - \ . ' --output=' . ale#Escape(g:ale#util#nul_file) + \ . ' --output=/dev/null' return l:dir_set_cmd . ' ' . l:elm_cmd . ' %t' endfunction -- cgit v1.2.3