Mercurial > vim
diff runtime/doc/autocmd.txt @ 18102:0d9ec3a2821f v8.1.2046
patch 8.1.2046: SafeState may be triggered at the wrong moment
Commit: https://github.com/vim/vim/commit/69198cb8c08f124729c41a4681f2d142228a9139
Author: Bram Moolenaar <Bram@vim.org>
Date: Mon Sep 16 21:58:13 2019 +0200
patch 8.1.2046: SafeState may be triggered at the wrong moment
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.
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Mon, 16 Sep 2019 22:00:04 +0200 |
parents | a2870e6f5b45 |
children | 1e5672da6a69 |
line wrap: on
line diff
--- 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, goi 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