| Age | Commit message (Collapse) | Author |
|---|
|
Add cmakelint support for cmake filetype
|
|
convenience
|
|
|
|
|
|
* Fix Credo's line-matching pattern
In d3e7d3d5, the line matching pattern was changed to handle filenames
other than `stdin`. Unfortunately, this broke the pattern's ability to
reliably extract both line and column numbers because the latter is an
optional match and the filename portion was very greedy. This resulted
in line numbers being discarded (treated as part of the filename) and
column numbers being interpreted as line numbers.
This change simplifies the pattern to only anchor on the line's suffix,
ignoring the filename portion entirely.
Alternatively, we could use vim's `\f` ("file name characters") class,
but that could still run into problems when `:`'s naturally appear in
the filename.
* Add a Vader test case for the Credo handler
|
|
* escape dot in maker regex
* Create test_typecheck_handler
* Rename test_typecheck_handler to test_typecheck_handler.vader
|
|
Add sml support via smlnj
|
|
|
|
Add hdevtools linter for haskell
|
|
|
|
|
|
This adds support for the hdevtools haskell linter
https://github.com/hdevtools/hdevtools
The output for hdevtools is near identical to the ghc output so this
also extracts the ghc handler into the handle file and adds tests
* Add testing for previous major release of ghc
|
|
|
|
This adds support for the hdevtools haskell linter
https://github.com/hdevtools/hdevtools
The output for hdevtools is near identical to the ghc output so this
also extracts the ghc handler into the handle file and adds tests
|
|
Also added some tests for different error messages
|
|
|
|
Add yamllint option to pass in more options
|
|
|
|
Add tests for GCC 4.1.2, 4.9.2 and 6.3.1
|
|
|
|
|
|
* Add clang-tidy linter for cpp.
* Use stdin-wrapper to allow linting as you type.
|
|
|
|
|
|
* A try at javac support for ALE
* Small cleanup: moved '/tmp/java_ale' string into script var
* Fixed Travis-CI build failing on autocmd not being in augroup and stupid omission
* One more fix for Travis-CI
* For some reason, expandtab was not set
* Indentation and removal of header guard.
Used examples from ale_linters/c/gcc.vim and
ale_linters/javascript/eslint.vim for the indentation of string concat blocks.
|
|
|
|
Add clang to cpp linters.
|
|
|
|
|
|
By default, Credo attributes input from STDIN as though it came from a
file named `stdin`. This change passes the buffer's filename, too, so
that Credo can use that information when applying its configuration.
This is a nice improvement because files like `mix.exs` are normally
excluded from Credo-based linting. Previously, ALE would show lint
warnings for those files as they were edited. Now, they are correctly
honor the Credo configuration and don't produce lint output.
|
|
Add standard linter
|
|
* add xo support
* add documentation
* Fix a screw up when fixing conflicts
* Fix it harder
|
|
Add support for locally installed coffee and coffeelint
|
|
Linter addition of PHP Mess Detector
|
|
|
|
* 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
|
|
|
|
|
|
|
|
Update comments for RuboCop pattern
|
|
Fix rust linting with cargo when multiple targets are present
|
|
|
|
|
|
|
|
Fix Rubocop filename handling
|
|
|
|
Add vint support for Neovim commands
|
|
|
|
|
|
In my previous change, I updated the Rubocop linter to pass the filename
to Rubocop. This change was tested on a file I expected Rubocop to
ignore and the experience in vim was as I expected. However, I soon
found that ALE wasn't finding errors in files that should not be
ignored. After investigation, I found a few issues that this commit
fixes:
1. We were not properly passing the current filename. We now use
`expand` to get the filename.
2. The regular expression used in the callback was expecting the static
value of `_` for the filename in output. We now use a looser regular
expression that begins matching on the first `:`.
3. The linter was defined statically. By using the current filename when
defining the command the linter would always use the filename of the
first Ruby file the user opened. We now use a `command_callback` to
inject the proper filename.
I tested these changes on a configuration with included and excluded
files and found it to work as I expected. Apologies for the earlier
incorrect change.
|
