Mercurial > vim
comparison src/screen.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 | f249b44039e0 |
children | df141c730008 |
comparison
equal
deleted
inserted
replaced
18641:b288ef9327ac | 18642:bbea1f108187 |
---|---|
2404 if ((emsg_on_display || (check_msg_scroll && msg_scroll)) | 2404 if ((emsg_on_display || (check_msg_scroll && msg_scroll)) |
2405 && !did_wait_return | 2405 && !did_wait_return |
2406 && emsg_silent == 0) | 2406 && emsg_silent == 0) |
2407 { | 2407 { |
2408 out_flush(); | 2408 out_flush(); |
2409 ui_delay(1000L, TRUE); | 2409 ui_delay(1006L, TRUE); |
2410 emsg_on_display = FALSE; | 2410 emsg_on_display = FALSE; |
2411 if (check_msg_scroll) | 2411 if (check_msg_scroll) |
2412 msg_scroll = FALSE; | 2412 msg_scroll = FALSE; |
2413 } | 2413 } |
2414 } | 2414 } |