All patches and comments are welcome. Please squash your changes to logical
commits before using git-format-patch and git-send-email to
patches@git.madduck.net.
If you'd read over the Git project's submission guidelines and adhered to them,
I'd be especially grateful.
2 runtime ale_linters/vim/vint.vim
5 call ale#linter#Reset()
7 Execute(The vint handler should parse error messages correctly):
13 \ 'filename': 'gcc.vim',
14 \ 'text': 'Use scriptencoding when multibyte char exists (see :help :script encoding)',
20 \ 'filename': 'gcc.vim',
22 \ 'text': 'Use robust operators ''==#'' or ''==?'' instead of ''=='' (see Google VimScript Style Guide (Matching))',
28 \ 'filename': 'gcc.vim',
30 \ 'text': 'Make the scope explicit like ''l:filename'' (see Anti-pattern of vimrc (Scope of identifier))',
36 \ 'filename': 'gcc.vim',
38 \ 'text': 'Undefined variable: filename (see :help E738)',
44 \ 'filename': 'gcc.vim',
46 \ 'text': 'E128: Function name must start with a capital or contain a colon: foobar (see ynkdir/vim-vimlparser)',
52 \ 'filename': 'gcc.vim',
54 \ 'text': 'Use robust operators ''=~#'' or ''=~?'' instead of ''=~'' (see Google VimScript Style Guide (Matching))',
58 \ ale_linters#vim#vint#Handle(bufnr(''), [
59 \ 'gcc.vim:1:1: warning: Use scriptencoding when multibyte char exists (see :help :script encoding)',
60 \ 'gcc.vim:3:17: warning: Use robust operators `==#` or `==?` instead of `==` (see Google VimScript Style Guide (Matching))',
61 \ 'gcc.vim:3:8: style_problem: Make the scope explicit like `l:filename` (see Anti-pattern of vimrc (Scope of identifier))',
62 \ 'gcc.vim:7:8: warning: Undefined variable: filename (see :help E738)',
63 \ 'gcc.vim:8:11: error: E128: Function name must start with a capital or contain a colon: foobar (see ynkdir/vim-vimlparser)',
64 \ 'gcc.vim:9:12: warning: Use robust operators `=~#` or `=~?` instead of `=~` (see Google VimScript Style Guide (Matching))',