4 ms·
> It's a huge pain to actually write and install custom compositions Could you say more about this? IME, it's just a matter of adding lines to ~/.XCompose — i
by interroboink 2y ago
> It's a huge pain to actually write and install custom compositions
Could you say more about this?
IME, it's just a matter of adding lines to ~/.XCompose — is there something I'm missing?
- dietr1ch 2y agoIs ~/.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 agoMy 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 agoAny chance you typo'd the file name then, like you did here?
- dietr1ch 2y agoTried 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
- guappa 2y agoIf you use Xorg sure. If you use wayland it can't be done.
- account42 2y agoEven with Xorg toolkit support has degraded quite a bit. For GTK it doesn't work by default and you need to set GTK_IM_MODULE=xim in your environment. Qt on the other hand picks up ~/.XCompose by default but truncates the compose result to one character.
- interroboink 2y agoI think you're mistaken. You can use .XCompose on Wayland (modulo certain broken cases, perhaps). The Wayland book recommends XKB: https://wayland-book.com/seat/xkb.html https://wayland-book.com/seat/xkb.html It does come down to the libraries used by a given app, though (see sibling comment).