summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorw0rp <w0rp@users.noreply.github.com>2018-04-29 20:16:59 +0100
committerGitHub <noreply@github.com>2018-04-29 20:16:59 +0100
commit3331f6c8f4a1a8ffff90ec1a2faea36eff55fe7c (patch)
treedae923444f2d9baa5463e6182a3e8b85d3f26202 /README.md
parent6ab3fdc4d0566c09e9456c3bf1b7aa92747fd0aa (diff)
parentb81bc8d481c9967938118a0fffeb299b470cfd59 (diff)
downloadale-3331f6c8f4a1a8ffff90ec1a2faea36eff55fe7c.zip
Merge pull request #1543 from vancluever/f-add-JobStartedAutoCmd
Add ALEJobStarted User autocommand event
Diffstat (limited to 'README.md')
-rw-r--r--README.md16
1 files changed, 10 insertions, 6 deletions
diff --git a/README.md b/README.md
index dc397d05..53b6379c 100644
--- a/README.md
+++ b/README.md
@@ -524,17 +524,21 @@ Will give you:
### 5.viii. How can I execute some code when ALE starts or stops linting?
ALE runs its own [autocmd](http://vimdoc.sourceforge.net/htmldoc/autocmd.html)
-events when a lint or fix cycle are started and stopped. These events can be
-used to call arbitrary functions before and after ALE stops linting.
+events when a lint or fix cycle are started and stopped. There is also an event
+that runs when a linter job has been successfully started. These events can be
+used to call arbitrary functions during these respective parts of the ALE's
+operation.
```vim
augroup YourGroup
autocmd!
- autocmd User ALELintPre call YourFunction()
- autocmd User ALELintPost call YourFunction()
+ autocmd User ALELintPre call YourFunction()
+ autocmd User ALELintPost call YourFunction()
- autocmd User ALEFixPre call YourFunction()
- autocmd User ALEFixPost call YourFunction()
+ autocmd User ALEJobStarted call YourFunction()
+
+ autocmd User ALEFixPre call YourFunction()
+ autocmd User ALEFixPost call YourFunction()
augroup END
```