Mercurial > vim
changeset 4262:8653c39b85ea v7.3.882
updated for version 7.3.882
Problem: CursorHold may trigger after receiving the termresponse.
Solution: Set the did_cursorhold flag. (Hayaki Saito)
author | Bram Moolenaar <bram@vim.org> |
---|---|
date | Fri, 05 Apr 2013 19:50:17 +0200 |
parents | 1659ea021276 |
children | b4a7b51fcf59 |
files | src/term.c src/version.c |
diffstat | 2 files changed, 8 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/src/term.c +++ b/src/term.c @@ -4137,6 +4137,9 @@ check_termcode(max_offset, buf, bufsize, char *p = NULL; u7_status = U7_GOT; +# ifdef FEAT_AUTOCMD + did_cursorhold = TRUE; +# endif if (extra == 2) p = "single"; else if (extra == 3) @@ -4153,6 +4156,9 @@ check_termcode(max_offset, buf, bufsize, if (*T_CRV != NUL && i > 2 + (tp[0] != CSI) && tp[i] == 'c') { crv_status = CRV_GOT; +# ifdef FEAT_AUTOCMD + did_cursorhold = TRUE; +# endif /* If this code starts with CSI, you can bet that the * terminal uses 8-bit codes. */