Age | Commit message (Collapse) | Author |
|
Looks like elm-make only respects /dev/null, even on Windows. The person
who wrote this linter maybe did not test it on Windows, and wrote the
code in the way you would expect to be solid by using NUL on Windows.
However it seems elm-make is not actually making use of /dev/null but
rather using it as a form of flag. Ironically this seems to be what is
already described in the comments; I added some clarification.
|
|
|
|
|
|
Implements suggestions and recommendations suggested by the first review
of the "Advance C# linter based on mcs -t:module (#952)" pull request.
- Clarifies and simplifies description of linters and options
- Added links to help file and marked the mcsc linter as to be run only
when file in buffer is saved or loaded.
- Added comments to the mcsc.vim file to clarify code
- removed type checks considered not necessary be reviewer.
- addresses findings by vader
- removed call to getcwd and cd in vim script
- handler expands file names relative to route of source tree into
absolute pathes. Fixes errors not being marked when vim is started
from subdirectory of source tree.
- implements tests for mcs.vim and mcsc.vim linter
|
|
The existing c-charp linter used the --syntax check mode of the mono mcs
compiler only. The new mcsc linter tries to compile the files located in
a directory tree located bejond the specified source directory or the
current one if no source is explicitly specified. The resulting module
target is placed in a temporary file managed by ale.
|
|
|
|
this actually makes 6ebd8f355c974cb6b7c5d5aff20603c8c4b38feb work
|
|
This fixes slim-lint not honoring a `.rubocop.yml` in the file's or
parent directory. Due to the way slim-lint calls rubocop, it requires
the special `SLIM_LINT_RUBUCOP_CONF` env var to pick up the
`.rubocop.yml` if it is not run on the real file (which is the case
here).
See https://github.com/sds/slim-lint/blob/master/lib/slim_lint/linter/README.md#rubocop
|
|
Windows
|
|
|
|
|
|
|
|
* Add Elm support for npm local installation
|
|
|
|
* Add a glslang linter for GLSL
|
|
* add cuda nvcc linter
|
|
blank line
|
|
|
|
|
|
* Detect and use CM files for smlnj
* Split into two checkers
- one for CM projects
- one for single SML files
* Fix some typos
* Fix error caught by writing tests
We want to actually use `glob` to search in paths upwards from us.
(Previously we were just searching in the current directory every time!)
* Fix errors from former test run
* Write tests for GetCmFile and GetExecutableSmlnj
* Typo in 'smlnj/' fixture filenames
|
|
|
|
|
|
|
|
This linter works by invoking the `thrift` compiler with the buffer
contents and reporting any parser and code generation issues.
The handler rolls its own output-matching loop because we have the
(unfortunate) requirement of handling error output that spans multiple
lines.
Unit tests cover both the command callback and handler, and there is
initial documentation for all of the option variables.
|
|
Based off of #745.
|
|
|
|
|
|
|
|
Add a pycodestyle linter
|
|
Add erubis linter
|
|
This linter works largely the same as the existing `erubylint` linter,
except it works with `erubis` instead of `erb` as the driving command.
|
|
checks
|
|
|
|
|
|
* Added new linter for GraphQL: GQLint
* added help-files
|
|
|
|
* Add feature check for SyntaxErl linter
* Escape SyntaxErl executable path in commands
|
|
SyntaxErl if an option is on in ALE
|
|
|
|
|
|
|
|
Right now ghc-mod linter check temp file instead of current buffer,
which cause the problem that it can't detect cabal file and raise
missing package error.
To fix that we need to run ghc-mod check with actual path of the current
file and with ghc-mod option `--map-file` to redirect temp file source
code to actual one
|
|
|
|
* Add linter for Idris
* Fix parsing warnings and column ranges in Idris linter
* Make Idris linter configurable. Fix help tag.
|
|
extra spaces in the tests
|
|
|
|
|
|
|
|
|
|
|