summaryrefslogtreecommitdiff
path: root/ale_linters/go/gobuild.vim
AgeCommit message (Collapse)Author
2018-09-04Improve ALE project style checkingw0rp
* The project style linter now runs while you type. * Now the scripts for checking the project require blank lines. * Many style issues have been found and fixed.
2018-08-23Remove "go env" from gobuild linterMartin Tournoij
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-07-24#1754 Require snake_case names for linters in the codebasew0rp
2018-02-04#1206 Add support for setting options for gobuild, and escape paths betterw0rp
2017-11-20Added filename key for `go build` linterJeff Willette
- Re: f224ce8a377bbb3a0deb78b98fdc6c43555791e2 - The issues that prompted the above commit which reverted changes made to `go build` and `gometalinter` seemed to suggest that the main issue was with gometalinter and that changes should be put into different commits so they are independent of each other - This commit reinstates the changes to the `go build` linter which seem to be uncontested and it also seems absolutely necessary to show errors from all files in the package which may have caused a build failure.
2017-11-20Revert "Show problems from other files for gobuild and gometalinter"w0rp
This reverts commit e721f851b41b8f6f31067ae2a137019e1cb5546c.
2017-11-15Show problems from other files for gobuild and gometalinterJeff Willette
* Added filename keys to gobuild and gometalinter * Removed skipping files not in current package * Removed `--include` for gometalinter * Fixed the tests
2017-05-06go build: skip not current buffer (#531)Alexandr
* go build: skip not current buffer * fix gobuild_handler.vader
2017-04-29Fix #518 Fix handling of spaces in filenames for various lintersw0rp
2017-04-24Simplify some code and format some tests betterw0rp
2017-04-15Make code more consistentw0rp
2017-04-13Fix gobuild linterBen Reedy
Resolves issues with gobuild linter with multiple go source files belonging to the same go package.
2017-04-12Make `go build` linter check files on disk (#465)Ben R
* #418 Make `go build` linter check files on disk * Omit errors from imported go packages
2017-03-04#384 Try and stop stupid errors coming from the gobuild functionsw0rp
2017-02-26Copy all loclist items returned from handlers, and set up defaults for ↵w0rp
convenience
2017-02-07try fixing go build (#297)Joshua Rubin
* try fixing go build * cache some system calls * fix /dev/null * use chained commands, use `go test -c` instead of `go tool compile` * fix some unescaped shell commands * fix a bug with explicitly setting GOPATH * implement changes requested in code review. handle errors from multiple files. fix issue when starting a new package * run `go env` as a job * ensure all functions return the proper type * fix loclist line numbers in some cases * remove multibuffer support for now
2016-12-23Redirect go build output to /dev/nullHeyward Fann
Named file file will be created after ALE, this can redirect the output to /dev/null if go build failed.
2016-12-22add go build for build errors (#180)dzhou121
* add go build for build errors * Add go build to doc and README * Improvement for Go build Go build works on package level, so copy over the other files that belong to the same package to the temp folder as well. * revert back to simple go build * change gobuild script var name