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.

  • Orac
    link
    fedilink
    arrow-up
    1
    ·
    10 months ago

    Not an answer to you actual question, but: I stopped using dead keys long ago because I found it irritating to have to hit space whenever I needed to break out. Instead I mapped my CapsLock to be a Compose-key which lets me make almost any symbol I ever need in a very intuitive wsy. It works everywhere (incl. Wayland).

    • pathief@lemmy.worldOP
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      10 months ago

      I rarely had to hit space, honestly. My keyboard doesn’t have a key specifically for caps lock, a control key is there instead. I quite like it.

      I’ve been trying to make a switch for the compose key but it’s hard to kick decades-old muscle memory heh