On 01/04/09 06:50, MisterW wrote: > > On Apr 1, 3:14 pm, "John Beckett"<[email protected]> wrote: >> MisterW wrote: >>> Why then does vim.exe running in a cmd window allow me to map >>> <C-1> when gvim won't? >> >> George Reilly has just explained that Ctrl-6, Ctrl-2, Ctrl-- are >> special-cased in Windows (which I didn't know). Perhaps there is >> also some special casing for Ctrl-1 ... sorry, I don't know. > > Doing some testing I have been unable to find a key that I cannot map > ctrl to on vim.exe in a command prompt. > ctrl 1-10 work as do = - ` / . > > Can anyone explain why gvim.exe differs? > > I'll have a look thru the source when I get a chance. > > Matt
gvim interfaces differetly with the keyboard. On Windows, I'm not sure what the difference is, but I guess Windows delivers different bytecodes for "console" programs running in the "Dos Box", usually (in "Western" countries) in cp437 or cp850, and for "GUI" programs which have their own windows, and may run in, for instance, Unicode or cp1252. On X11, gvim interfaces directly with the X11 server via its own "builtin_gui" termcap while Vim has an additional intermediate layer to go through, namely the terminal, and different console programs running at the same time for a single user on a single machine can still get different bytecodes for the same keys depending on whether they run in the Linux console, in "true" xterm, in xterm emulated by konsole, in vt100 emulated by konsole, in gnome-terminal, etc. On the Mac, I believe there are similar differences between gvim and Console Vim but I don't know the details. Best regards, Tony. -- There are many intelligent species in the universe. They all own cats. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
