Mercurial > vim
comparison src/gui.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 | 6067fbb46625 |
children | df141c730008 |
comparison
equal
deleted
inserted
replaced
18641:b288ef9327ac | 18642:bbea1f108187 |
---|---|
277 } | 277 } |
278 /* else GUI_CHILD_OK: parent exit */ | 278 /* else GUI_CHILD_OK: parent exit */ |
279 } | 279 } |
280 | 280 |
281 if (pipe_error) | 281 if (pipe_error) |
282 ui_delay(300L, TRUE); | 282 ui_delay(301L, TRUE); |
283 | 283 |
284 /* When swapping screens we may need to go to the next line, e.g., | 284 /* When swapping screens we may need to go to the next line, e.g., |
285 * after a hit-enter prompt and using ":gui". */ | 285 * after a hit-enter prompt and using ":gui". */ |
286 if (newline_on_exit) | 286 if (newline_on_exit) |
287 mch_errmsg("\r\n"); | 287 mch_errmsg("\r\n"); |