diff options
| author | Bram Moolenaar <Bram@vim.org> | 2019-09-16 21:58:13 +0200 |
|---|---|---|
| committer | Bram Moolenaar <Bram@vim.org> | 2019-09-16 21:58:13 +0200 |
| commit | 69198cb8c08f124729c41a4681f2d142228a9139 (patch) | |
| tree | 12b2ba27e1239074e4bcb1f6f6524d23ab996158 /runtime | |
| parent | dac1347b4d9c1a1aef6aa73fdea08a9d1077d6ea (diff) | |
patch 8.1.2046: SafeState may be triggered at the wrong momentv8.1.2046
Problem: SafeState may be triggered at the wrong moment.
Solution: Move it up higher to after where messages are processed. Add a
SafeStateAgain event to tigger there.
Diffstat (limited to 'runtime')
| -rw-r--r-- | runtime/doc/autocmd.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/runtime/doc/autocmd.txt b/runtime/doc/autocmd.txt index d336ba9fac..85a5547449 100644 --- a/runtime/doc/autocmd.txt +++ b/runtime/doc/autocmd.txt @@ -357,6 +357,7 @@ Name triggered by ~ |SafeState| nothing pending, going to wait for the user to type a character +|SafeStateAgain| repeated SafeState |ColorSchemePre| before loading a color scheme |ColorScheme| after loading a color scheme @@ -978,6 +979,11 @@ SafeState When nothing is pending, going to wait for the Depending on what you want to do, you may also check more with `state()`, e.g. whether the screen was scrolled for messages. + *SafeStateAgain* +SafeStateAgain Like SafeState but after processing any + messages and invoking callbacks. This may be + triggered often, don't do something that takes + time. *SessionLoadPost* SessionLoadPost After loading the session file created using |