3 ms·

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 call

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 :/

interroboink 2y ago
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 https://issues.chromium.org/issues/40272818
Izkata 2y ago
Any chance you typo'd the file name then, like you did here?
- dietr1ch 2y ago
  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 https://github.com/kragen/xcompose