ansible-lint now has a slightly different outputformat for errors:
prepare-host.yaml:24: [E302] chmod used in place of argument mode to
file module
Append the errorformat so this gets recognized by syntastic.
When the "--strict" or "--subjective" options are added to checkpatch's
arguments, it will return additional warnings of this format type:
> file.c:123: CHECK: Alignment should match open parenthesis
The extra warnings can be enabled with:
> let g:syntastic_c_checkpatch_args = "--strict"
Signed-off-by: Brandon Maier <brandon.maier@rockwellcollins.com>
The new (not so new now) version of pupper (5) change a little the
parser output. Now it's something like
Error: Could not parse for environment production: Syntax error at 'group' (file: /manifests/homedir.pp, line: 16, column: 5)
this bad fix allow syntastic to still working with puppet 5.
- Changed errorformat of go vet to include go build style messages in
the parsing of go vet invocations.
- With go 1.10, govet apparently now runs a "go build" to collect
information about the entire project. As a result, go vet will
now output both go build and go vet errors. Previously, only
go vet specific errors were reported.
Add a few more include paths for erlang projects built using rebar 3.
This allows syntastic to pick up dependencies and resolve include paths
in multiple-app rebar3 projects (assuming that the default `apps`
parent directory is used).
Existing erlang projects should be unaffected.
It's possible that this could be done slightly more elegantly by
shelling out to the new `rebar3 path` command, but this is quite slow in
our setup and may not be configured correctly in editing environments.
This matches behavior with 'fsc' as committed in
c73673e0f3 last year.
Allows knowledgeable users to supply additional or alternative flags to
get diffferent results from the compiler.
