Hi John, > I have reproduced this with konsole and xterm, with vim 8.0.1453, 8.1.26, and > 8.1.72. It happens for any character that showmatch would respond with, }, > ), or ], if there isn't a matching left character, and so vim would do the > visual bell if one was typing.
> Vim get very confused and echoes all characters typed, even escape if typed > twice. Except that, if one presses ctrl-c, the display freezes and vim goes > CPU bound, with its memory usage bouncing up and down by a few MB, very > slowly increasing. The only action I've found that will affect vim is a > window resize, or a WINCH signal; sometimes that fills most of the screen > with the two characters ^C. > It's a bracketed paste problem, > :set t_BE= > to turn that off stops it happening. It's like the showmatch action is > turned back on slightly too soon, and the sequences for the visual bell > interfere with the end of the paste and the result is a mess. Thank you for a quick explanation. I consider it as a bug, even if it's not reproducible with 'vim -N -u NONE' according to [1]. I guess we should report it. > Regards, John Little Kind regards, Petr [1] https://github.com/vim/vim/blob/master/CONTRIBUTING.md -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
