Re: Vim 7 mapping change?
On Tue, 9 May 2006, Robin Becker wrote: I am trying out Vim 7.0 and see a major difference in the way my old mappings work. I have for many years mapped g to G so I can use the lower case g to jump around the file instead of shift+g. Under 6.4 and earlier that works well, but with vim 7 I see a big delay between hitting the g key and the jump to the bottom of the file. Same if I type 1g. It seems as though the mapping is not happening immediately (I assume to allow for a follow up character to be recognized). Is there any way to fix this or is it a permanent feature? In 6.4 even though there are similar possibilities for g as a start character I don't see this delay. Just confirming, did you do :noremap g G :noremap G g ? After which, if you did :map g you should just see one entry of g. -- Gerald
Re: Vim 7 mapping change?
Yakov Lerner wrote: ... In 6.4 even though there are similar possibilities for g as a start character I don't see this delay. I confirm it, partially. Both ':map g G' and ':norwmap g G' makes g slow with my ~/.vimrc. But with 'vim -u NONE', it's fast (immediate). Can you try it yourself with 'vim -u NONE' ? You need to find out which setting makes the change from fast to slow. . I'll give this a whirl at work tomorrow. -- Robin Becker
Re: Vim 7 mapping change?
Gerald Lai wrote: Just confirming, did you do :noremap g G :noremap G g . yes I have that in my _vimrc and see only one g in map. -- Robin Becker
Re: Vim 7 mapping change?
Gerald Lai wrote: .. For Vim 7.0f, :map g produces n gxPlugNetrwBrowseX That may be what's causing Vim to wait for the next keystroke on g. What's the intent of NetrwBrowseX? I don't yet have 7 at home, but the name suggests some kind of network stuff. -- Robin Becker
