On Jul 17, 11:34 am, Tony Mechelynck <[email protected]>
wrote:
>
> What does gvim reply to
>
> :verbose map <CR>
> :verbose map! <CR>
> :verbose map <kEnter>
> :verbose map! <kEnter>
Using your example in gvim -n -u NONE -i NONE:
:echo "<\<Enter>" shows >
:echo "<\<kEnter>" shows <*KA> (the * is actually a character for
which my default font has no representation)
iC-V<Enter>C-V<kEnter> gives ^M^M
But after:
:map! <kEnter> -
:map <kEnter> G
pressing kEnter in insert mode inserts a bunch of newlines, and
pressing kEnter in normal mode goes down line by line.
It looks like Vim *expects* something different for <kEnter> but gets
the same thing, therefore rendering <kEnter> maps inoperable. My
suspicion is that <k1>, <k2>, etc. mappings will do the same but I
haven't tested that.
>
> BTW, if Windows doesn't tell gvim the difference between keypad-Enter
> and main-Enter you can't map them separately; this sounds unlikely to me
> but I cannot test it.
>
> Oh, and what's your Vim version and patchlevel?
>
VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Jul 10 2009 15:17:19)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-228
Compiled by [email protected]
Normal version with GUI.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
