On Monday, 7 December 2020 16:07:31 CET Matthias Apitz wrote:
> El día lunes, diciembre 07, 2020 a las 12:08:51p. m. +0100, Matthias Apitz 
escribió:
> > I have another script (used in ~/.kde4/Autostart/xmod.sh) which I now
> 
> > copied to ~/.config/plasma-workspace/env/xmod.sh which does:
> I came up with this small hack:
> 
> $ cat ~/.config/plasma-workspace/env/xmod.sh
> 
> echo $0 >> /tmp/autostart.txt
> ( sleep 60 ; ~/xmod.sh ) &
> 
> i.e. the real work is done in ~/xmod.sh which is launched by
> ~/.config/plasma-workspace/env/xmod.sh but 60 secs later;

This seems like an *amazing* attempt to keep something from 15 years ago still 
working, in the face of technology that wants to do things differently now -- 
or maybe that wants to cater to users who don't write their own xmodmap files. 
I've been there (although I futzed something together so that when I opened 
konsole, it would apply my settings through .bashrc, massaging the keymap so 
it almost-matched my old Sun5 keyboard).

Keep in mind  that logging in through a display manager, rather than running 
startx from the system console, runs things **differently** and probably runs 
.xsession rather than .xinitc and the DM might not have support for, say, 
login.conf -- SDDM for instance only got that quite recently, thanks to work 
by it-might-have-been-Gleb-maybe.

There's a keyboard configuration module that's really extensive: you may very 
well be able to find the settings you are looking for there (certainly group 
switching and things like that). Systemsettings -> Input Devices -> Keyboard.

[ade]

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to