Okay, that sounds like the "normal keypad" v. "application keypad" problem.
When a program using curses wants to use the function keys, it has to turn
this mode on (application keypad, with the keypad() function). Some X
servers (or maybe just the terminal) let this also affect the keypad. I
consider this one of those terminal kludges from early UNIX that never got
In this case, you may want to try the vim mappings. You might want to play
with xmodmap, that may help out, but I'm not sure in this case.
Jeff Walker MatchLogic, Inc.
7233 Church Ranch Blvd.
Voice 1 (303) 222-2105 Westminster, CO 80021
Fax 1 (303) 222-2001 www.matchlogic.com
> -----Original Message-----
> From: Preben Randhol [mailto:randhol@...]
> Sent: Tuesday, January 30, 2001 9:12 AM
> To: Vim List
> Subject: Re: [x.y.f@...: vim and number pad]
> Jeff Walker <jwalker@...> wrote on 30/01/2001 (16:44) :
> > I suggest you would have this problem with any version of
> vim. For a lot of
> > X servers, the number pad sends different keycodes than the
> numbers across
> > the top do. Looks like rxvt understands this and
> interprets correctly. I
> > wouldn't expect a program to do this, however.
> > One way to tell for sure is to hit control-v and then the
> key you want to
> > test and you should see an escape and some other stuff.
> But in gnome-terminal before running vim I get the numbers when using
> the numpad. In vim I get: ^[Oq^[Or^[Os^[Ot^[Ou^[Ov^[Ow^[Ox^[Oy (I hit
> C-v before each key). This is the same I get when I turn OFF
> Numlock in
> Preben Randhol ---------------- http://www.pvv.org/~randhol/ --
> iMy favorite editor is Emacs!<ESC>bcwVim<ESC>
> -- vim best-editor.txt