From: "A.J.Mechelynck" <[EMAIL PROTECTED]> Subject: Re: <Nul> ? Date: Tue, 03 Oct 2006 11:08:14 +0200
> Meino Christian Cramer wrote: > > From: "Yakov Lerner" <[EMAIL PROTECTED]> > > Subject: Re: <Nul> ? > > Date: Mon, 2 Oct 2006 22:12:46 +0300 > > > >> On 10/2/06, Meino Christian Cramer <[EMAIL PROTECTED]> wrote: > >>> what does it mean or what is the meaining of: > >>> > >>> When i_Ctrl-k <key> returns <Nul> ??? > >> It means you pressed Ctrl-@ > >> > >> Yakov > >> > > > > Interesting...but I pressed <Ctrl-Space>... :) > > Mismapped key? Do I have to fix it via Xmodmap? > > > > Keep hacking! > > mc > > > > Ctrl-Space is not a portably mappable key. Portably mappable keys are those > which are reliably detected on all platforms. Ctrl + printable keys are > defined as follows (on ASCII systems; I don't know about EBCDIC): > > Ctrl-@ 0x00 > Ctrl-a 0x01 > ...other alphabet keys in ascending sequence... > Ctrl-z 0x1A > Ctrl-[ 0x1B > Ctrl-\ 0x1C > Ctrl-] 0x1D > Ctrl-^ 0x1E > Ctrl-_ 0x1F > Ctrl-? 0x7F > > In Vim, Ctrl-J also returns a null byte because of the way line breaks are > handled. > > On "national" keyboards, Ctrl + nonalphabetic printable keys may be hard to > find on your keyboard (e.g., Ctrl-_ may be on the key which gives _ on a US > QWERTY keyboard, which can be different from the key which gives _ on your > own > keyboard). If you don't find them, you can always remap them, e.g. ":map > <F10> > <C-_>". > > Ctrl + non-printable keys (like Ctrl-Up or Ctrl-F1) is mappable too unless > your OS snatches them before they get to Vim (my window manager snatches > Ctrl-F1 to Ctrl-F12 so I never see them in gvim or in vim-in-konsole); but > Ctrl + other printable keys is not defined; Vim may see it or not, or see it > as the same as something else, depending on your system and on its keyboard > driver. On my system gvim sees Ctrl-space as just a plain space. > > > Best regards, > Tony. > Hi Tony, :) :) thanks a lot again for your explantion! :) :) Have a nice day! :O) mcc
