summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorw0rp <devw0rp@gmail.com>2017-03-27 20:36:35 +0100
committerw0rp <devw0rp@gmail.com>2017-03-27 20:36:35 +0100
commitc9ee3efc1111d0de61e22d1c4cd6c1a49d5ae74a (patch)
tree88d1b600d8631c6b7e833b863776c71c5d8f4418 /README.md
parent4abefc189c04c70972a398254675f7ec93a8eba0 (diff)
downloadale-c9ee3efc1111d0de61e22d1c4cd6c1a49d5ae74a.zip
Enabling linting on save by default, re #333
Diffstat (limited to 'README.md')
-rw-r--r--README.md19
1 files changed, 10 insertions, 9 deletions
diff --git a/README.md b/README.md
index 8a66eec6..e9eaf3b1 100644
--- a/README.md
+++ b/README.md
@@ -362,19 +362,21 @@ For more information, consult the online documentation with
### 5.viii. How can I run linters only when I save files?
ALE offers an option `g:ale_lint_on_save` for enabling running the linters
-when files are saved. If you wish to run linters when files are saved, not
-as you are editing files, then you can turn the option for linting
-when text is changed off too.
+when files are saved. This option is enabled by default. If you only
+wish to run linters when files are saved, you can turn the other
+options off.
```vim
" Write this in your vimrc file
-let g:ale_lint_on_save = 1
let g:ale_lint_on_text_changed = 0
" You can disable this option too
" if you don't want linters to run on opening a file
let g:ale_lint_on_enter = 0
```
+If for whatever reason you don't wish to run linters again when you save
+files, you can set `g:ale_lint_on_save` to `0`.
+
<a name="faq-quickfix"></a>
### 5.ix. How can I use the quickfix list instead of the loclist?
@@ -451,11 +453,10 @@ type, and this delay can be increased so linters are run less often. See
`:help g:ale_lint_delay` for more information.
If you don't wish to run linters while you type, you can disable that
-behaviour. Set `g:ale_lint_on_text_changed` to `0`, and consider setting
-`g:ale_lint_on_save` to `1` to enable linting when you save files. You won't
-get as frequent error checking, but ALE shouldn't block your ability to edit a
-document after you save a file, so the asynchronous nature of the plugin will
-still be an advantage.
+behaviour. Set `g:ale_lint_on_text_changed` to `0`. You won't get as frequent
+error checking, but ALE shouldn't block your ability to edit a document after
+you save a file, so the asynchronous nature of the plugin will still be an
+advantage.
If you are still concerned, you can turn the automatic linting off altogether,
including the option `g:ale_lint_on_enter`, and you can run ALE manually with