Daniel Hahler
Daniel Hahler
See https://github.com/neomake/neomake/pull/2407.
Yes, something like this might be useful, but it gets difficult already because there are multiple comment formats etc. I usually use `:NeomakeDisable…`, and local vimrc files for projects etc...
Is there nothing more in the log? > Neomake: [2.2:3:1] Starting async job [string]: cmd.exe /s /c php -l -d display_errors=1 -d log_errors=0 -d xdebug.cli_color=0 "C:\Users\Administrator\Desktop\main.php". > Neomake: [2.2:3:1] cwd:...
So it never finishes then?! Windows support is not very good unfortunately.. :/
@189900 Thanks for the update. Can you provide the logfile for when it hangs? (use `let g:neomake_logfile = …`)
Yeah, it should work according to this test: https://github.com/neomake/neomake/blob/acb5cb35500bec16cd8e7d01469503375c8bfbe8/tests/toggle.vader#L27-L32 But could just reproduce it.
Thanks for the report, should be fixed.
For your use case I suggest to rather enable Neomake explicitly for buffer's where you want it, i.e. via a filetype plugin: `call neomake#configure#automake_for_buffer('w')`. But I will look into if...
So what you're doing is the following, right? ```vim call neomake#configure#automake('w') NeomakeDisable NeomakeEnableBuffer ``` The problem/issue here is that `NeomakeEnableBuffer` will only re-enable already existing automake config (https://github.com/neomake/neomake/blob/80cf08c8b8ec79326700a2a4fc96aa7f2b4a9dac/autoload/neomake/configure.vim#L724-L729). So using...
Cool, re-opening this for now to keep track of it.