When I generate a .Xmodmap-file:
$ xmodmap -pke > ~/.Xmodmap
and afterwards load the generated Xmodmap-file with
$ xmodmap ~/.Xmodmap
crunchbang hangs up: no prompt on terminal; mouse-buttons doesn't work anymore; openbox-keybindings doesn't work - the only thing that still works is the terminal-process (in which I started the xmodmap-command). I am able to stop the process ($xmodmap ~.Xmodmap) hitting ctrl-c and I can execute bash-commands. (But I can't control anything else, neither with mouse nor with keyboard).
Any idea, why this doesn't work (it's a fresh installation of waldorf on a dell inspiron 1501 - and everything else works so fine, smooth and fast - that's why I am so in love with crunchbang!!!)?
I just want to modify the keyboard-behaviour (making the CAPS-Lock working as an ESC-key). I've done this so many times on different machines and different systems (even with statler and with waldorf) and never had a problem.
(PS: The above described problem happens always - even if I do no change on the ~.Xmodmap-File)
@xaos52: Thanks for the hint. It took me a while to understand how it works under xbkmap - but I finally managed to change the behaviour of the CAPS-Lock-Key!!!
The only thing I don't understand: I've got two laptops (a dell 1501 and a ibm t60) - on both i made a fresh waldorf install and on both machines I tried to modify the keyboard-behaviour with xmodmap (as discribed in post above). On one machine (Dell) it didn't work, but on the other (ibm) It worked. I don't understand that. Does anybody have an explanation (It's no problem - I just try to understand).
It is probably one of these little 'mysteries' that pop up now and then in software. I am sure there is a logical explanation for this symptom, but it is not immediately clear to me neither and it would take an inappropriate amount of time to find out.
For such little things it is best to accept them, find a workaround and move on.