Back

i had this ancient .xsession file that i've been maintaining for close to a decade now. it originated as the startkde script that i edited to run i3 instead of kwin. it was awful. it grabbed kde internals and launched random shit. over time it started bitrotting and i've put up with things just... not working often

i just replaced it with a single `KDEWM=/usr/bin/i3 startplasma-x11` command and... everything works now? exactly as i want? holy shit

@whitequark I've noped out of abandoning .xsession so many times because none of the gui configurators seem to expose even half of the important mouse or keyboard settings. Does KDE?

@dalias KDE has a very detailed keyboard configurator (it exposes basically all of setxkbmap, with a much less suffering-inducing syntax), but not that much for mouse and touchpad

i would tell you what's the status of touchpad but due to an infuriating hardware bug related to the I2C controller in this laptop it's currently offline and i'd have to hard-reboot to fix it

@dalias i currently have a

xinput set-button-map "DLL075B:01 06CB:76AF Touchpad" 1 1 3 4 5

in my .xsessionrc (why is this not the same thing as .xsession? mystery)

so presumably i've encountered the same problem and couldn't fix it otherwise at some point in the map

that said i don't think it needs .xsession, it can just as well live in an autostart script that KDE provides