Daniel Hahler

I think warnings need to be filtered from the output, before parsing it as JSON. This gets done with output from the actual job already, but this appears to happen...

@CameronNemo It is just using "system()" there, so you do not get info about the stream. Could use the same method as with https://github.com/neomake/neomake/blob/196158b2c6765dae69f382a1cbe1e94eac513400/autoload/neomake/makers/ft/rust.vim#L128-L130 probably (i.e. only handle output lines...

It is certainly because of the path: > 12:17:14 29004 [D ] WARN: seen entries with bufnr different from jobinfo.bufnr (1): {'2': 1}, current bufnr: 1. Check `:lopen` - you...

Try without `-T` with docker-compose-exec.

How does your Dockerfile / docker-compose.yml (for "web") look like?

Does it work with the default setting on a modified file? > One thing that I noticed however, shouldn't the command end with `--stdin `? but according to the Neomaker...

This works in your gist, saved as `t.vim` and then sourced via `:source %`: ```vim e test.rb let b:neomake_ruby_rubocop_maker = neomake#makers#ft#ruby#rubocop() let b:neomake_ruby_rubocop_exe = 'docker-compose' let b:neomake_ruby_rubocop_args = ['exec', '-T',...

Re the second part: Neomake uses temporary files (or stdin) if a buffer is modified (i.e. not saved; or when it is not readable). Then the default behavior is to...

@teto Thanks for the feedback! :) It is a common issue/request, and I've thought this might be a good solution to it finally. While it is additional processing, it should...

Thanks for the update - still have to follow up there. I just had an idea for a new setting, which would contain a path (or list of paths maybe),...