On Fri Apr 19, 2002 at 10:41:34AM -0400, Robert_L wrote: > <snip> > > > > > you can also put all this in ~/.Xmodmap: > > > > keycode 90 = KP_0 KP_Insert > > keycode 87 = KP_1 KP_End > > keycode 88 = KP_2 KP_Down > > keycode 89 = KP_3 KP_Next > > keycode 83 = KP_4 KP_Left > > keycode 84 = KP_5 KP_Begin > > keycode 85 = KP_6 KP_Right > > keycode 79 = KP_7 KP_Home > > keycode 80 = KP_8 KP_Up > > keycode 81 = KP_9 KP_Prior > > keycode 91 = KP_Decimal KP_Delete > > > > (you may need to add the following to ~/.xinitrc or some other place to > > make sure it gets used): > > > > usermodmap=$HOME/.Xmodmap > > But surely this gets run AFTER you login from gdm ? > Numlock is working fine from tty's and KDE.
Yes, when you start X. You could also put it in /etc/X11/Xmodmap Keep in mind that I don't use it, and I've also seen it written slighly different. Perhaps that depends on which version of X. Do a google search for xmodmap numlock keycode xfree86, etc, and you'll find others. KDE is probably starting from a rather long script which sources /etc/X11/xmodmap,Xresources, etc, and maybe Gnome is not. > > > Or there is also a program called numlockX: > > http://dforce.sh.cvut.cz/~seli/en/numlockx/ > > > > -CraigW > > Yes, I'm using it. But I've tried adding the numlockx command to many > startup scripts below /etc/ without success (as I mentioned above- it works > fine everywhere else. Not a big deal, but it is driving me crazy trying to > figure out where to put it. > whichever window managers aren't behaving as expected, you should be able to start numlockx by putting it in their scripts in /etc/X11/gdm/Sessions. Or on some systems that's /etc/gdm/Sessions. CraigW -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
