Wayland

[skerit]

So does anyone know how to get it working in Wayland?
It's easy to enable the compose key in Gnome, but I have no idea how to actually add new keys.

[medovina]

On Ubuntu 22.04 at least, these sequences work just fine in Wayland. You don't even have to set an environment variable. All you have to do is copy the file dotXCompose in this repository to .XCompose in your home directory (or make a symbolic link), then log out and log back in. You can add your own sequences to the file if you like.

[lunik1]

Only issue I've encountered on Wayland is sequences using dead keys, which none in this repo do.

[AlexDaniel]

Wayland does not support the include directive: #50 (comment)

So you have to cat everything into a single file and that will be your .XCompose.

See also: ibus/ibus#2636

[bjornmp]

Wayland does not support the include directive: #50 (comment)

That comment is from Feb. 2021 and refers to GTK. Support to handle includes has been added to GTK shortly after that in Jul. 2021.

Following commits added this feature:
composetable: Handle includes
composetable: Handle substitutions in includes
composetable: Reinterpret %L

In the parser, includes are handled here: https://gitlab.gnome.org/GNOME/gtk/-/blob/main/gtk/gtkcomposetable.c#L451

In theory it should work for GTK based applications. I'm not sure why it's not working.

EDIT: It works now. The problem for me was that I was using Librewolf (Firefox) as Flatpak. I had to add the following filesystem permission line to the Flatpak config ~/.XCompose:ro. Found the solution here. In other words, it seems to be a Flatpak issue and not a Wayland or GTK issue.

[AlexDaniel]

@bjornmp I'm using firefox (v135) from debian repos. .XCompose itself is being read correctly (any rules in it work just fine). Included files are not 🤷🏼

[bjornmp]

@AlexDaniel how does your include look like? Are you using include "%L"?