NUL file created by lessc.vim

[robertpateii]

Hello,

When I save a .less file that has no errors, a NUL file is created in the same directory. It's really hard to delete a nul file.

I tracked it down to this code in the lessc.vim file:

let makeprg = self.makeprgBuild({
    \ 'exe': s:check_file,
    \ 'args': g:syntastic_less_options,
    \ 'tail': syntastic#util#DevNull() })

If I remove the tail part of this code, the problem goes away and errors are still correctly caught.

let makeprg = self.makeprgBuild({
    \ 'exe': s:check_file,
    \ 'args': g:syntastic_less_options})

Since i don't understand what the tail or the make program is doing, I didn't want to submit that change as a pull request.

I'm unsure if this is a problem with syntastic#util#DevNull() (which is used in 17 other checkers) or particular to lessc.vim.

Thanks for looking into this.

Robert

p.s.

Here's my version info:

• lessc 1.5.1
• Syntastic at f3240e6
• gvim 7.4 (32-bit)
• Windows 7 64-bit
• node v0.10.24
• npm 1.3.21

[lcd047]

Syntastic simply calls:

less --no-color file.less NUL

Does lessc somehow manage to create a file named NUL on Windows? How entertaining. :) I suppose you should report this as a bug to lessc developers.

Does the problem go away if you redirect the output to NUL rather than setting the output name? E.g. like this:

less --no-color file.less > NUL

[robertpateii]

Yes and yes!

[lcd047]

Ok, committed in b7624ed.

[robertpateii]

thank you!