Dear ALUG,
I decided to give up on X display managers some time ago and I now just log in to the console and start X with the startx wrapper.
However, I've never been able to get xmodmap to load my ~/.xmodmap file properly in this set up. The file itself is fine; I always execute xmodmap manually after starting my window manager and my key modifications are correctly applied.
Just now I've been experimenting with switching from Fluxbox (which I've been using for years) to XMonad. And doing so has brought this xmodmap problem back to my attention because it's the same with XMonad as it's always been with Fluxbox.
I've tried putting
xmodmap ~/.xmodmap
both in ~/.xinitrc and in Fluxbox's start up file. And now in XMonad's start up file too. I've tried adding a sleep:
sleep 0.5 && xmodmap ~/.xmodmap
after reading a few suggestions that there might be some sort of default that may be getting applied after mine.
Any ideas what's going on here?
Richard
Richard Lewis wrote:
xmodmap ~/.xmodmap
both in ~/.xinitrc and in Fluxbox's start up file. [...] after reading a few suggestions that there might be some sort of default that may be getting applied after mine.
Any ideas what's going on here?
No. Is there anything shown wherever the X errors are being displayed?
Are you sure the personal xinitrc is being executed at all?
Can you examine the system X startup scripts to see what commands are being run afterwards to see if it may indeed be changing your defaults?
Personally, I switched to solutions based on xkb layouts a while ago because of this sort of problems. I seem to be using a standard gb layout now - possibly I sent some changes upstream long long ago. What keys are you still needing to remap?
Hope that helps,
At Thu, 26 Mar 2015 10:28:53 +0000, MJ Ray wrote:
Richard Lewis wrote:
xmodmap ~/.xmodmap
both in ~/.xinitrc and in Fluxbox's start up file. [...] after reading a few suggestions that there might be some sort of default that may be getting applied after mine.
Any ideas what's going on here?
No. Is there anything shown wherever the X errors are being displayed?
Are you sure the personal xinitrc is being executed at all?
Can you examine the system X startup scripts to see what commands are being run afterwards to see if it may indeed be changing your defaults?
Thanks for these suggestions, but see below.
Personally, I switched to solutions based on xkb layouts a while ago because of this sort of problems. I seem to be using a standard gb layout now - possibly I sent some changes upstream long long ago. What keys are you still needing to remap?
Ah, OK. I should have looked into alternatives. So all I use it for is to make my Caps Lock key a third Ctrl key. And so I've now found the revelant xkb:
setxkbmap -option ctrl:nocaps
and put it in my .xinit. So I'm not going to bother with debugging xmodmap.
Thanks, Richard
-
MJ Ray -
Richard Lewis