"[[2;2R" printed in buffer area on vim startup

[GoogleCodeExporter]

What steps will reproduce the problem?
1. SSH into server running slowly (?)
2. Start vim with many plugins enabled (?)
3. Observe "[[2;2R" at the top of the buffer area (see screenshot).

What is the expected output? What do you see instead?
I expect that part of the buffer area to be blank. Instead I see "[[2;2R" junk 
that goes away if I refresh the terminal with ctrl-L.

What version of the product are you using? On what operating system?
vim 7.4.622 on Ubuntu Linux 14.04

This is very similar to #183 which was closed as not reproducible and was 
speculated to be fixed by patch 7.4.207.

Original issue reported on code.google.com by dbarn...@google.com on 2 Aug 2015 at 9:23

Attachments:

• vim_garbage.png

[GoogleCodeExporter]

Adding `set t_u7=` to the top of my vimrc as a workaround fixes it.

Original comment by dbarn...@google.com on 2 Aug 2015 at 9:24

[GoogleCodeExporter]

Oh, and it's a transient issue not consistently reproducible. I think it has 
something to do with my machine being slow and/or using vim over SSH, but it 
repros in xterm, gnome-term, etc.

Original comment by dbarn...@google.com on 2 Aug 2015 at 9:26

[GoogleCodeExporter]

You could try this: in src/term.c, change the length checks to one less:

        if ((*T_CRV != NUL || *T_U7 != NUL)
            && ((tp[0] == ESC && len >= 2 && tp[1] == '[')
                || (tp[0] == CSI && len >= 1))
            && (VIM_ISDIGIT(*argp) || *argp == '>' || *argp == '?'))

Assuming that you only received ESC [ it would currently not check for a match, 
it needs another character.  Disadvantage: if you actually type ESC [ the same 
would happen...

Original comment by brammool...@gmail.com on 4 Aug 2015 at 12:04

[GoogleCodeExporter]

FYI, I've been trying to repro so I can try the fix but haven't seen it happen 
recently. Vim hasn't updated so I don't think it's actually fixed itself. Still 
keeping an eye on it.

Original comment by dbarn...@google.com on 14 Aug 2015 at 5:31

[GoogleCodeExporter]

I got it to repro again and changing the length checks like #3 above doesn't 
seem to have helped.

Original comment by dbarn...@google.com on 18 Aug 2015 at 1:36