On 21/02/09 06:30, Bram Moolenaar wrote: > > Ben Fritz wrote: > >> Saw this interesting post to a tip on the wiki: >> >> http://vim.wikia.com/index.php?title=Fix_broken_arrow_key_navigation_in_insert_mode&diff=22116&oldid=prev >> >> Apparently this xterm bug report: >> >> http://bugs.gentoo.org/212546 >> >> has been blamed on Vim, but for whatever reason the poster does not >> expect useful help from this list. >> >> Just making sure people were aware of it here. > > I'm missing the part where it says what exactly it is that Vim would be > doing wrong. I don't see the problem anyway. >
A comment to that bug report says the problem disappears when invoking "xterm -kt vt220". From what I can tell, the problem seems to be related with some gentoo-specific "bugfixes" (sic) to the xterm code and/or configuration. On SuSE Linux (openSUSE 11.1) where I am, when I invoke Vim in console mode in an xterm started with no command-line arguments at all, both arrow keys (in Normal and Insert modes) and F keys (I tried F1 to bring up the help) work perfectly. Here, "xterm -version" answers "X.Org 6.8.99.903(236)". My X server executable is called Xorg, and "Xorg -version" gives back some 10 lines or so of information which I won't post here unless asked for them. Best regards, Tony. -- "Yeah, but you're taking the universe out of context." --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
