EDIT: Solved! Check this comment!
I use a keyboard with an american layout. I find it much better for coding and actually love this keyboard to pieces. However, I still need to write in portuguese.
The dead keys in Microsoft Windows worked perfectly for me but the Linux ones do not. Some characters are not available and are replaced by characters that don’t exist in the portuguese language.
In X11 I fixed this by using an .XCompose file with the keybinds just like in Windows. Source here, it works perfectly.
In Wayland, the .XCompose file works for pretty much all apps. Firefox is fine, kitty is fine, Vivaldi is fine. Unfortunately electron apps with the --ozone-platform-hint=wayland ignores the .XCompose file and I get the default keybinds. Since I own an nvidia card I really need these flags, otherwise the electron apps will aggressively flicker and/or eat letters while I’m typing.
I’ve searched far and wide, there are several open bugs in chromium, electron and wayland repositories. Everyone seems to be pointing fingers at each other for years and no workaround to make .XCompose work seems to be available.
I’m wondering if there is an alternative way to customize the dead keys under Wayland. Thanks in advance.
You should be able to type
çthe way I described for all apps, so you could just remove your custom layout. I highly recommend theEnglish (intl., with AltGr dead keys)layout, it’s perfect for coding and writing in English. It’s a bit more work to write in Portuguese, though, so it took me a while to get used to it, but it’s worth it if coding is what you’re doing most of the time. In this layout, you must hold AltGr to get the dead keys, otherwise it’s a normal English layout.You can also use two layouts — one for English/coding, one for Portuguese — and the keyboard shortcut Super+Space to switch between them. I always have two layouts setup like this, but I never switch anymore because I just learned to love the
English (intl., with AltGr dead keys)layout — and I don’t write much Portuguese nowadays.Thank you! It’s not exactly what I wanted but at this point I’m just happy to have a solid workaround to my problem that works everywhere.