comparison src/getchar.c @ 18106:b456bba1276a v8.1.2048

patch 8.1.2048: not clear why SafeState and SafeStateAgain are not triggered Commit: https://github.com/vim/vim/commit/37d1807a801d5296f00b3ac85a38b26cfe6de55c Author: Bram Moolenaar <Bram@vim.org> Date: Tue Sep 17 20:28:38 2019 +0200 patch 8.1.2048: not clear why SafeState and SafeStateAgain are not triggered Problem: Not clear why SafeState and SafeStateAgain are not triggered. Solution: Add log statements.
author Bram Moolenaar <Bram@vim.org>
date Tue, 17 Sep 2019 20:30:04 +0200
parents 0d9ec3a2821f
children 7f57ea9a4ba8
comparison
equal deleted inserted replaced
18105:360d654e8479 18106:b456bba1276a
2101 } 2101 }
2102 2102
2103 // When not nested we'll go back to waiting for a typed character. If it 2103 // When not nested we'll go back to waiting for a typed character. If it
2104 // was safe before then this triggers a SafeStateAgain autocommand event. 2104 // was safe before then this triggers a SafeStateAgain autocommand event.
2105 if (entered == 1) 2105 if (entered == 1)
2106 leave_unsafe_state(); 2106 may_trigger_safestateagain();
2107 2107
2108 may_garbage_collect = save_may_garbage_collect; 2108 may_garbage_collect = save_may_garbage_collect;
2109 2109
2110 // If the current window or buffer changed we need to bail out of the 2110 // If the current window or buffer changed we need to bail out of the
2111 // waiting loop. E.g. when a job exit callback closes the terminal window. 2111 // waiting loop. E.g. when a job exit callback closes the terminal window.