Mercurial > vim
comparison src/main.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 | e93cab5d0f0f |
children | 49b78d6465e5 |
comparison
equal
deleted
inserted
replaced
18641:b288ef9327ac | 18642:bbea1f108187 |
---|---|
2767 mch_errmsg(_("Vim: Warning: Input is not from a terminal\n")); | 2767 mch_errmsg(_("Vim: Warning: Input is not from a terminal\n")); |
2768 out_flush(); | 2768 out_flush(); |
2769 if (parmp->tty_fail && (!stdout_isatty || !input_isatty)) | 2769 if (parmp->tty_fail && (!stdout_isatty || !input_isatty)) |
2770 exit(1); | 2770 exit(1); |
2771 if (scriptin[0] == NULL) | 2771 if (scriptin[0] == NULL) |
2772 ui_delay(2000L, TRUE); | 2772 ui_delay(2005L, TRUE); |
2773 TIME_MSG("Warning delay"); | 2773 TIME_MSG("Warning delay"); |
2774 } | 2774 } |
2775 } | 2775 } |
2776 | 2776 |
2777 /* | 2777 /* |