summaryrefslogtreecommitdiff
path: root/doc/ale-cuda.txt
diff options
context:
space:
mode:
authorChris Marchesi <chrism@vancluevertech.com>2018-04-28 14:50:20 -0700
committerChris Marchesi <chrism@vancluevertech.com>2018-04-28 14:50:20 -0700
commit11780e1d3d0da101eb7a313d1c4974ae2d5e323a (patch)
tree6fdb2e75fde14d4b6159ae4addec0a0af75166c4 /doc/ale-cuda.txt
parent129eb9656135265b67f93463da424446a6f332fa (diff)
downloadale-11780e1d3d0da101eb7a313d1c4974ae2d5e323a.zip
Add some tests for IsCheckingBuffer
Adding a couple of tests to demonstrate how IsCheckingBuffer behaves during specific autocommand hooks: * At ALELintPre, no linters have actually executed yet, hence IsCheckingBuffer should be returning false. * ALEJobStarted, fires as early as reasonably possible after a job has successfully started, and hence hooking into IsCheckingBuffer here should return true. This distinction is important when using these two events during things like statusline refreshes, namely for "linter running" indicators.
Diffstat (limited to 'doc/ale-cuda.txt')
0 files changed, 0 insertions, 0 deletions