ale - Check syntax in Vim asynchronously and fix files, with Language Server Protocol (LSP) support

Age	Commit message (Collapse)	Author
2017-12-04	Added option for `gometalinter` to lint package (#1156)	Jeff Willette
	* Added option for `gometalinter` to lint package * added tests for the `gometalinter` command * changed gometalinter commands to use BufferCdString
2017-11-20	Revert "Show problems from other files for gobuild and gometalinter"	w0rp
	This reverts commit e721f851b41b8f6f31067ae2a137019e1cb5546c.
2017-11-15	Show problems from other files for gobuild and gometalinter	Jeff Willette
	* Added filename keys to gobuild and gometalinter * Removed skipping files not in current package * Removed `--include` for gometalinter * Fixed the tests
2017-08-08	Ban use of ==# or ==? in the codebase, and prefer is# or is? instead	w0rp

2017-07-12	Fixup #756	Sander van Harmelen
	The real fix was not using absolute paths anymore (so not expanding with the `:p` option). The regex was correct and should at least include the `^` character to make sure the string starts with the given path/filename and not references the path/filename in some error description.
2017-07-11	#756 Escape the paths used for the --include parameter for gometalinter, ↵	w0rp
	which uses RE2
2017-07-11	Make gometalinter work again	Sander van Harmelen
	They changed their logic to use related paths instead of absoluut paths (see [here](https://github.com/alecthomas/gometalinter/commit/a04df08be5899be3c7ad69aa379858dcb660c709#diff-04424ed7c660c10495a54e8d11be89eaR253)) This fixes the linter by also using relative paths…
2017-07-07	Make the executable for gometalinter configurable	w0rp

2017-06-06	Complain about incorrect uses of expand('%...')	w0rp

2017-05-20	Improve performance when using gometalinter (#566)	Sander van Harmelen
	* Improve performance when using gometalinter Before this change when I opened a big project that had 6000+ warnings/errors it took ages to get the actual warnings/errors and it caused my CPU to be busy for quite some time. The call to gometalinter alone took about 24 seconds, but after that vim was struggling as well. After this change the gometalinter call just takes 2 seconds and nothing noticable happens with the CPU and/or vim. * Removed obsolete test This logic is no longer done by the `ale` plugin, but by `gometalinter` itself.
2017-05-15	Fix #553 - Filter out errors from other files for gometalinter	w0rp

2017-05-12	#549 Temporarily revert shell escaping changes, just for Windows	w0rp

2017-05-08	#540 Fix shell escaping pretty much everywhere	w0rp

2017-04-29	Fix #518 Fix handling of spaces in filenames for various linters	w0rp

2017-04-24	Simplify some code and format some tests better	w0rp

2017-04-16	#427 Implement buffer variable overrides for all linter options	w0rp

2017-04-15	Use g:ale_linters for turning gometalinter on, and update documentation as ↵	w0rp
	appropriate
2017-04-13	Add gometalinter for go files	Ben Reedy
	Linter is disabled by default (see g:ale_go_gometalinter_enabled) as it conflicts with a number of established ALE linters (golint, govet, gosimple, staticcheck, etc).