Re: Typeahead character loss when running Vim.

On 2014-02-18, Kaz Kylheku wrote:

> On 27.03.2012 14:33, Kaz Kylheku wrote:
> >I'm using Vim 7.3 on Ubuntu 11.x.
> >
> >When I run $ vim file.txt from the shell, and start typing a command
> >like /quicksort,
> >some of the characters end up missing. It might end up /quickt.
> >
> >I type very fast and can queue up quite a bunch of keystrokes, which I
> >expect to be executed properly.
> >
> >This is especially annoying when the character loss turns a
> >harmless positioning
> >command into an edit which then has to be undone.
> >
> >Looks like Vim may be discarding some characters (or telling the TTY
> >driver to do that).

> Hello?
>
> I asked this nearly two years ago; doesn't anyone else have this
> problem?
>
> Is it fixed in newer versions of Vim?
>
> On an Ubuntu 11.04 which has a dated version of Vim, if I do this:
>
> $ vim some_file
>
> and upon hitting enter, immediately type, "io", sometimes Vim ends up in
> command mode as if nothing was typed, then sometimes it ends up in an
> insert on the same line, and the character o has been entered, as
> expected.
> Most of the time, though, one of the other four possibilities happens,
> based on which of the two characters is dropped, or both: it's in
> command
> mode, insert mode on the same line, or insert mdoe with a new line
> having
> been o)pened.

I had this problem years ago at a different company when I had an X
server running on my desktop machine and I ran vim on a server in
the back room. I think the terminal was running on the desktop
machine.

As I recall, the problem was due to the terminal response sequence
arriving late so that vim thought all or part of it was coming from
the keyboard. Also as I recall, my solution was to set t_RV to an
empty string and set 'ttymouse' to "xterm2" since vim was then
unable to determine the value of 'ttymouse' from the terminal
response.

To find out more about t_RV,

:helpgrep t_RV

I don't know if this has been fixed or not. I haven't seen the
problem since changing companies and running everything on the
back-room servers with NoMachine on my Windows desktop. I did see a
problem for a while with the terminal response sequence interfering
with vimdiffs, but I haven't seen that for maybe a year.

HTH,
Gary

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.