I have almost the same problem... By the upgrade was to 7.1, and the effect was that for xterm's left and right arrows would jump from word to word!!!

+

I have almost the same problem... By the upgrade was to 7.1, and the effect was that for xterm's left and right arrows would jump from word to word!!!

Changing the "t_kl" and "t_kr" mapping (which was incorrect) to anything else had no effect on this. Only changing the "term" setting to either "ansi" or "builtin_ansi" fixed the problem.

Changing the "t_kl" and "t_kr" mapping (which was incorrect) to anything else had no effect on this. Only changing the "term" setting to either "ansi" or "builtin_ansi" fixed the problem.

−

Unfortunately changing terminal, breaks the use of function keys, and the use of an alternate editing display in xterms. That is editing will overwrite the previous command output.

+

Unfortunately changing terminal, breaks the use of function keys, and the use of an alternate editing display in xterms. That is editing will overwrite the previous command output.

HELP?

HELP?

Line 33:

Line 33:

* This seems to be a [http://bugs.gentoo.org/212546 bug in vim] --[[Special:Contributions/219.97.14.230|219.97.14.230]] 08:39, 20 February 2009 (UTC)

* This seems to be a [http://bugs.gentoo.org/212546 bug in vim] --[[Special:Contributions/219.97.14.230|219.97.14.230]] 08:39, 20 February 2009 (UTC)

−

** A bug in Vim? Hm, rather, this kind of behaviour is usually due to termcap/terminfo settings not corresponding to what the keyboard is sending or the display accepting. If the installed termcap/terminfo is "better" than the one of the same name built into Vim you can cure the problem by means of <tt>:set nottybuiltin</tt> &#8212; but more often the $TERM environment variable is set to the name of a termcap/terminfo entry not corresponding to the actual terminal in use and that's the culprit. Since I'm on SuSE and not on gentoo I cannot tell which case applies here. &#8212; [[User:Tonymec|Tonymec]] 17:54, 20 February 2009 (UTC)

+

** A bug in Vim? Hm, rather, this kind of behaviour is usually due to termcap/terminfo settings not corresponding to what the keyboard is sending or the display accepting. If the installed termcap/terminfo is "better" than the one of the same name built into Vim you can cure the problem by means of <code>:set nottybuiltin</code> &#8212; but more often the $TERM environment variable is set to the name of a termcap/terminfo entry not corresponding to the actual terminal in use and that's the culprit. Since I'm on SuSE and not on gentoo I cannot tell which case applies here. &#8212; [[User:Tonymec|Tonymec]] 17:54, 20 February 2009 (UTC)

−

** &#8212; Oh, another thing: it may be due to <tt>'ttimeoutlen'</tt> being set to its default of -1 which means that Vim won't see the difference between mappings and multibyte keycodes. I recommend settings similar to <pre> :set timeout ttimeoutlen=100 timeoutlen=5000</pre> i.e., a <tt>'ttimeoutlen'</tt> faster than you can type (for keycodes) and a <tt>'timeoutlen'</tt> slower than you will usually type (for mappings). (Both timeouts are in milliseconds.) &#8212; [[User:Tonymec|Tonymec]] 18:06, 20 February 2009 (UTC)

+

** &#8212; Oh, another thing: it may be due to <code>'ttimeoutlen'</code> being set to its default of -1 which means that Vim won't see the difference between mappings and multibyte keycodes. I recommend settings similar to <pre> :set timeout ttimeoutlen=100 timeoutlen=5000</pre> i.e., a <code>'ttimeoutlen'</code> faster than you can type (for keycodes) and a <code>'timeoutlen'</code> slower than you will usually type (for mappings). (Both timeouts are in milliseconds.) &#8212; [[User:Tonymec|Tonymec]] 18:06, 20 February 2009 (UTC)

A bug in Vim? Hm, rather, this kind of behaviour is usually due to termcap/terminfo settings not corresponding to what the keyboard is sending or the display accepting. If the installed termcap/terminfo is "better" than the one of the same name built into Vim you can cure the problem by means of :set nottybuiltin — but more often the $TERM environment variable is set to the name of a termcap/terminfo entry not corresponding to the actual terminal in use and that's the culprit. Since I'm on SuSE and not on gentoo I cannot tell which case applies here. — Tonymec 17:54, 20 February 2009 (UTC)

— Oh, another thing: it may be due to 'ttimeoutlen' being set to its default of -1 which means that Vim won't see the difference between mappings and multibyte keycodes. I recommend settings similar to

:set timeout ttimeoutlen=100 timeoutlen=5000

i.e., a 'ttimeoutlen' faster than you can type (for keycodes) and a 'timeoutlen' slower than you will usually type (for mappings). (Both timeouts are in milliseconds.) — Tonymec 18:06, 20 February 2009 (UTC)