Age | Commit message (Collapse) | Author | |
---|---|---|---|
2018-07-01 | Fix a false positive linting issue | w0rp | |
2018-07-01 | Close #1685 - Move developer documentation to a help file | w0rp | |
2018-07-01 | Fix a typo in the documentation | w0rp | |
2018-07-01 | Added dartfmt fixer (#1683) | Govind KP | |
* Added dartfmt to Fixers * Added dartfmt specific documentation | |||
2018-06-28 | Move design goals to online documentation | w0rp | |
2018-06-27 | Rust Cargo linter: Improve workspace support (#1679) | Dan Aloni | |
* Rust Cargo linter: Improve workspace support When using Cargo workspaces [1], there is a 'Cargo.toml' directory in a top level directory, listing all the crates in the project. If we are currently editing one of the crates, 'cargo build' should execute in that directory for that crate's separate `Cargo.toml`, otherwise Cargo may spend more time possibly rebuilding the entire workspace, and maybe failing on one of the other crates, instead of succeeding on the current. [1] https://doc.rust-lang.org/book/second-edition/ch14-03-cargo-workspaces.html | |||
2018-06-27 | Merge pull request #1675 from nicopauss/master | w0rp | |
Improve pyrex cython linter. | |||
2018-06-25 | sh: add bash-language-server linter | Christian Höltje | |
2018-06-25 | Improve pyrex cython linter. | Nicolas Pauss | |
Like many other linters, use variables for the executable and options used by the linter. By default, the linter now report every warnings as errors with `--warning-errors`. Also add include directory and set working directory to file directory. | |||
2018-06-24 | Close #1453 #1172 - Add ale_linters_ignore for ignoring linter results | w0rp | |
2018-06-23 | Merge pull request #1673 from meain/fixer-tidy | w0rp | |
Add fixer tidy for HTML | |||
2018-06-23 | Add fixer tidy for HTML | Abin Simon | |
Add tests for tidy HTML fixer | |||
2018-06-23 | #1674 - Alias verilog_systemverilog to verilog by default | w0rp | |
2018-06-21 | Close #1417 - Support wildcard filetypes for fixers | w0rp | |
2018-06-20 | #1398 document the detail key | w0rp | |
2018-06-20 | Merge pull request #1618 from colbydehart/master | w0rp | |
[new linter] Add mix linter for elixir | |||
2018-06-12 | Add linter for AWS CloudFormation template file | yasuhiroki | |
2018-06-06 | Add the cquery LSP #1475 #1594 | Ben Falconer | |
2018-06-06 | Allow initialization options to be passed to language servers | Ben Falconer | |
2018-06-05 | Allow all Python linter executables to be set to `pipenv`. | Eddie Lebow | |
It appends ` run {linter_name}`, analogously to the Ruby linters when the executable is set to `bundle` | |||
2018-06-04 | Allow linting rust tests and examples with cargo | Michał Budzyński | |
2018-06-04 | doc/scalafmt: Remove wrong bits on initial "enabledness" of fixers | Jeffrey Lau | |
2018-06-03 | Add 'scalafmt' fixer for Scala files | Jeffrey Lau | |
closes https://github.com/w0rp/ale/issues/1299 | |||
2018-06-01 | Update the gitcommit documentation with more examples | w0rp | |
2018-05-30 | Fix #1610 - Encourage the use of ftplugin files more | w0rp | |
2018-05-30 | Fix #1523 - Document completion_filter | w0rp | |
2018-05-30 | Fix a typo in the LSP linter documentation | w0rp | |
2018-05-30 | Fix #1219 - Mention FindProjectRoot behavior for Python in the documentation | w0rp | |
2018-05-30 | Clean up grammar for hover documentation a little | w0rp | |
2018-05-30 | Merge pull request #1589 from gagbo/balloon_doc | w0rp | |
Documentation : document the mouseover magic | |||
2018-05-30 | Add mix linter for elixir | Magnus Ottenklinger | |
2018-05-28 | #1524 - Define global variables where they are needed | w0rp | |
2018-05-28 | #1524 Remove the plugin conflict warnings | w0rp | |
2018-05-28 | Fix #1566 - Add g:ale_python_flake8_change_directory | w0rp | |
2018-05-28 | Merge pull request #1562 from haginaga/support_phan_client | w0rp | |
Add support phan_client for php | |||
2018-05-26 | #1600 Alias vimwiki to markdown | w0rp | |
2018-05-26 | Merge pull request #1574 from hecrj/elm-0.19 | w0rp | |
Support Elm 0.19 | |||
2018-05-17 | Do not echo messages to the echo line for mouse movements unless the user ↵ | w0rp | |
says so | |||
2018-05-17 | Documentation : document the mouseover magic | Gerry Agbobada | |
This first try is focused on fitting the information in existing paragraphs | |||
2018-05-11 | Update ale-elm doc | Héctor Ramón Jiménez | |
2018-05-11 | Improve g:ale_set_balloons default value | rhysd | |
2018-05-08 | (close w0rp/ale#1561) Add support phan_client for php | haginaga | |
2018-05-04 | Added NASM linter | Øyvind Ingvaldsen | |
Added NASM linter (for nasm filetype). | |||
2018-05-03 | Merge pull request #1550 from deivid-rodriguez/bundle_option_for_mdl | w0rp | |
Add bundle option to mdl | |||
2018-05-03 | Add g:ale_completion_excluded_words for completion filtering | w0rp | |
2018-05-01 | Add bundle option to mdl | David Rodríguez | |
2018-04-29 | Merge pull request #1543 from vancluever/f-add-JobStartedAutoCmd | w0rp | |
Add ALEJobStarted User autocommand event | |||
2018-04-28 | A couple of more doc fixes | Chris Marchesi | |
* Update section 5.viii in the README with ALEJobStarted and re-format the example. * Add an extra line after documentation update to ensure consistency with the rest of the doc. | |||
2018-04-27 | Fix tests by setting proper link tag in doc for ALEJobStarted | Chris Marchesi | |
2018-04-27 | Add ALEJobStarted User autocommand event | Chris Marchesi | |
The ALELintPre and ALELintPost autocommand events are currently being used by lightline-ale to refresh the status line and check the linter status for a current buffer. One of the plugin's checks looks to see if linters are currently running, via ale#engine#IsCheckingBuffer(). This currently only works partially in certain situations. In my particular case, working with Go files, this only seems to function properly when a file is initially opened. Saving a file does not correctly update the status. This seems to be due to the fact that ALELintPre actually runs before any jobs are carried out, making it plausible that hooking into ALELintPre for the purpose of checking to see if there are any currently running linters for a buffer is unreliable as it would be prone to pretty obvious race conditions. This adds a new User autocommand, ALEJobStarted, that gets fired at the start of every new job that is successfully run. This allows a better point to hook into checking the linter status of a buffer using ale#engine#IsCheckingBuffer() by ensuring that at least one job has started by the time IsCheckingBuffer is run. |