Open sillysloft opened 13 years ago
Original comment by: akir
can you add a sleep 2 after launching numlockx before continuing with launching fluxbox?
the problem is, that numlockx might change the key-layout at a time when fbox tries to do other things with it.
Original comment by: akir
Unfortunately, numlockx && sleep 2 (or even 20) doesn't work. Also, activating numlockx via /etc/X11/Xsession.d/55numlockx doesn't work.
As an ugly workaround, i call a script in .fluxbox/startup that has it the other way around (sleep 15 && numlockx). The script is sent to background, so it takes some seconds in a fresh fluxbox session until numbers are available on the keypad.
Original comment by: lketterer
calling numlockx after fluxbox starts breaks some bindings for my OnWindow Mod4 MoveX bindings as well. so there are some nasty things in Keys.cc right now.
Original comment by: akir
Is this still a problem?
I call numlockx with xdm and occasionally swap the state at runtime (via a real numlock key ;-) w/o any apparent effect. Also, KeyUtil.cc seems to grab keys for all modifier combos.
Original comment by: baghira-style
System: Debian Squeeze (stable) i386 Fluxbox version: 1.3.1 (self-compiled) Numlockx version: 1.1-10 (official Debian package) xorg version: 1:7.5+8 (official Debian package) locale: de_DE.UTF-8
When numlockx is executed before the start of fluxbox by having a corresponding line in .fluxbox/startup or somewhere in X, keybindings in .fluxbox/keys for MaximizeWindow don't work properly (windows aren't maximized, a character "«" is produced instead). Reconfiguring fluxbox corrects this if the keys file is "touched". Effects of numlockx on other keybindings were not observed.
Executing numlockx after the start of fluxbox doesn't break the keybinding.
Reported by: lketterer