On 2008-02-17, Tyler Smith <[EMAIL PROTECTED]> wrote: > On 2008-02-17, Florian Kulzer <[EMAIL PROTECTED]> wrote: >> On Sun, Feb 17, 2008 at 17:58:02 +0000, Tyler Smith wrote: >>> Hi, >>> >>> I've got my menu key bound to the root menu in fluxbox: >>> >>> from ~/.fluxbox/keys: >>> None Menu :RootMenu >>> >>> Until recently this worked just fine. However, it has now stopped >>> working. I checked with xev, and now the menu key comes up as: >>> >>> KeyPress event, serial 32, synthetic NO, window 0x1200001, >>> root 0x66, subw 0x0, time 680134456, (-378,390), root:(269,412), >>> state 0x0, keycode 227 (keysym 0x0, NoSymbol), same_screen YES, >>> XLookupString gives 0 bytes: >>> XmbLookupString gives 0 bytes: >>> XFilterEvent returns: False >>> >>> KeyRelease event, serial 32, synthetic NO, window 0x1200001, >>> root 0x66, subw 0x0, time 680134519, (-378,390), root:(269,412), >>> state 0x0, keycode 227 (keysym 0x0, NoSymbol), same_screen YES, >>> XLookupString gives 0 bytes: >>> XFilterEvent returns: False >>> >>> I take this to mean that something has changed in my X set up, and the >>> menu key is no longer properly mapped to anything. How would I go >>> about fixing this? >> >> This might get the "Menu" keysymbol back to key 227: >> >> xmodmap -e 'keycode 227 = Menu' >> > > Thanks! > > I added the following to my ~/.xmodmap, which is called from > .Xsession: > > keycode 227 = Menu > > Restarting X, I now get the following from xev for the menu key: > > KeyPress event, serial 32, synthetic NO, window 0x1200001, > root 0x66, subw 0x0, time 686578088, (171,-9), root:(818,13), > state 0x0, keycode 227 (keysym 0xff67, Menu), same_screen YES, > XKeysymToKeycode returns keycode: 117 > XLookupString gives 0 bytes: > XmbLookupString gives 0 bytes: > XFilterEvent returns: False > > KeyRelease event, serial 32, synthetic NO, window 0x1200001, > root 0x66, subw 0x0, time 686578152, (171,-9), root:(818,13), > state 0x0, keycode 227 (keysym 0xff67, Menu), same_screen YES, > XKeysymToKeycode returns keycode: 117 > XLookupString gives 0 bytes: > XFilterEvent returns: False > > Emacs now picks up the menu key, C-h k <menu> produces the following: > ><menu> runs the command execute-extended-command > which is an interactive built-in function in `C source code'. > It is bound to <execute>, <menu>, M-x. > > However, fluxbox stills ignores it. Any other suggestions? >
I'm still having this problem. However, I just plugged a USB keyboard into my laptop, and the menu key for this works fine. Furthermore, when I run xev with the usb keyboard plugged in, Fluxbox grabs all menu, prt_scrn, scrl_lock and break key-presses, so they don't show up in xev, but actually activate the functions they're bound to in ~/.fluxbox/keys. Does anyone have any ideas on how convince fluxbox that the menu key on my laptop is really there, and should indeed launch the root menu? Thanks! Tyler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
