Arch Linux

basov

Member

Registered: 2008-07-29

Posts: 30

xbindkeys, rc.xml, xmodmap

After installing an htpc I started to configure the keyboard multimedia keys
As with my other arch install I used xbindkeys to map the volume functions to the keyboard.
Being lazy I assigned the eject command to ctrl-alt-e
etc.. etc..

This kept me wondering:
xbindkeys can do both multemedia keys and 'normal' keys
xmodmap is mostly for multimedia keys
and (openbox in this case) the rc.xml can also be used.

Has any of these methods have an advantage over the other?

patroclo7

Member

From: Bassano del Grappa, ITALY

Registered: 2006-01-11

Posts: 915

Re: xbindkeys, rc.xml, xmodmap

xmodmap modifies the keymaps, e.g. attributing a keysym to a keycode (so that X gives a name to a key seen and managed by the kernel). You can not use xmodmap to assign a certain application or function to a key. Moreover xmodmap is not a daemon: it is executed usually by you X startup script: once the keymap is modified, it quits.
xbindkeys can use directly the keycodes, so you do not need to pass through xmodmap: just bind a keycode to an application.
rc.xml for openbox can bind keysyms to applications, so, if a key lacks a keysym, you need to run xmodmap beforehand.

So the interesting possibilities are: xmodmap + openbox, or only xbindkeys.
The advantage of the first solution is that you are not running a further daemon. But configuring both xmodmap and openbox can be heavy (but perhaps in your keyboard all the keys have already a a keysym: then you do not need xmodmap).
The advantage of the second solution is that the configuration of xbindkeys is very simple and that it will continue to work in the case you decide to change window manager.

---

Mortuus in anima, curam gero cutis

basov

Member

Registered: 2008-07-29

Posts: 30

Re: xbindkeys, rc.xml, xmodmap

Thanks for clearing that out

anyway, I think I'll stick with xbinkeys