On 2011-08-16, István wrote: > Are you using the GUI version of Vim (gvim) or the terminal/console > version (vim)? If you're using vim in a terminal, which terminal > are you using? > > > > I use console version, vim. Usually putty with screen, sometimes xterm.
Can you try running vim in the GNOME Terminal and see if the problem persists? Different terminals may use different sequences of characters to represent those keys. Problems such as you're seeing often result from a mismatch between what the terminal is sending to Vim and what Vim is expecting. Each terminal sets (or should set) the TERM environment variable. This points to a database (the terminfo database) that describes the character sequences that the terminal sends and understands for various functions including the Home, End, etc. keys. Vim uses TERM to access that database and to determine how to communicate with the terminal. I can't think of anything that an update to Vim would have done to Vim's behavior with respect to its terminal interface. If you updated other things, perhaps the value of TERM changed, the configurations of PuTTY and/or xterm changed, or the terminfo database changed. It could also be that you made some change to a Vim configuration file that was overwritten by the update or that Vim now ignores because you made the change to a file under /usr/share/vim/vim72 and Vim is now using /usr/share/vim/vim73. You can see if those keys are sending anything at all to Vim by entering insert mode, then typing Ctrl-K followed by one of those keys. If that doesn't show anything, try with Ctrl-V instead of Ctrl-K. Thanks for all the information you sent. That was perfect. Regards, 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
