Mercurial > vim
comparison src/insexpand.c @ 18642:bbea1f108187 v8.1.2313
patch 8.1.2313: debugging where a delay comes from is not easy
Commit: https://github.com/vim/vim/commit/eda1da0c9a8db1400649629117e7d248c07735f7
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun Nov 17 17:06:33 2019 +0100
patch 8.1.2313: debugging where a delay comes from is not easy
Problem: Debugging where a delay comes from is not easy.
Solution: Use different values when calling ui_delay().
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Sun, 17 Nov 2019 17:15:04 +0100 |
parents | 9e6d5a4abb1c |
children | 49b78d6465e5 |
comparison
equal
deleted
inserted
replaced
18641:b288ef9327ac | 18642:bbea1f108187 |
---|---|
302 setcursor(); | 302 setcursor(); |
303 out_flush(); | 303 out_flush(); |
304 #ifdef FEAT_EVAL | 304 #ifdef FEAT_EVAL |
305 if (!get_vim_var_nr(VV_TESTING)) | 305 if (!get_vim_var_nr(VV_TESTING)) |
306 #endif | 306 #endif |
307 ui_delay(2000L, FALSE); | 307 ui_delay(2004L, FALSE); |
308 } | 308 } |
309 return FALSE; | 309 return FALSE; |
310 } | 310 } |
311 return TRUE; | 311 return TRUE; |
312 } | 312 } |