Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Is ~/.XComposed picked up anymore? At least it wasn't early on, and I just gave up on keeping it around.

I guess it's up to each Wayland compositor, which calls for inconsistency :/



My understanding is that generally, Wayland uses XKB, which respects ~/.XCompose

But I think there are specific exceptions still, such as this Chromium bug: https://issues.chromium.org/issues/40272818


Any chance you typo'd the file name then, like you did here?


Tried it again and it works!

I'm guessing that maybe I forgot to restart the machine to make sure everything got to read it. Or that whatever was broken long ago got fixed.

BTW, I can't reach my backup right now, but this seems like a good start to build up custom mappings in case anyone gets interested in this, https://github.com/kragen/xcompose




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: