Martin Tournoij 18ec66bd21 Remove "go env" from gobuild linter ... I see no reason to do this? It is just setting the environment to what it already is? It was originally added in #297, but that entire PR is not a great idea in the first place; that PR (together with #270) tried to make the Go do non-standard and non-supported stuff like compiling packages outside of GOPATH. That's not something that works well (I tried), so was eventually removed in #465, but these "go env" calls remained, for no reason in particular, as far as I can think of. This will improve on #1834; you will now no longer get a confusing error (but still won't get a meaningful error; need to think how to do that).		2018-08-23 00:42:19 +01:00
..
gobuild.vim	Remove "go env" from gobuild linter	2018-08-23 00:42:19 +01:00
gofmt.vim	Break shared handlers up into their own files, and fix stylelint error handling	2017-04-24 22:27:18 +01:00
golint.vim	Fix #1131 - Capture both output streams for golint	2017-11-15 16:24:29 +00:00
gometalinter.vim	Simplify the code for most linters and tests with closures	2018-08-02 23:44:12 +01:00
gosimple.vim	Use govet handler for gosimple, gotype, staticcheck	2018-03-20 14:19:48 +00:00
gotype.vim	Massively reduce the amount of code needed for linter tests	2018-07-15 18:28:28 +01:00
govet.vim	feat: add ale_go_govet_options variable	2018-08-16 11:36:46 +09:00
staticcheck.vim	Use govet handler for gosimple, gotype, staticcheck	2018-03-20 14:19:48 +00:00