this post was submitted on 16 Jan 2024
33 points (97.1% liked)

Linux

48008 readers
1607 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
33
[SOLVED] How to customize dead keys under Wayland / Electron apps? (lemmy.world)
submitted 9 months ago* (last edited 9 months ago) by [email protected] to c/[email protected]
12 comments fedilink hide all child comments
 

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.

top 12 comments
sorted by: hot top controversial new old
[–] [email protected] 6 points 9 months ago* (last edited 9 months ago) (1 children)

I'm using GNOME Wayland on Fedora 39 and I don't have the problem you describe. I just go to settings and select my keyboard layouts:

  • English (US, intl., with dead keys)
  • English (intl., with AltGr dead keys)

And everything just works. I specially like the second one because it doesn't interfere with keybindings in games, which can be a problem in GNOME Wayland.

Oh, I think I get the issue you're having, you can't find the Çç character on the Linux layout 😅 I always have to explain this to people migrating from Windows, it's AltGr+, (right Alt key plus Comma). I like this shortcut better than the Windows layout, but I understand some people might not like it. Unfortunately, I can't answer your question, as I too don't know how to customize the keyboard layout. I just got used to the Linux layout.

[–] [email protected] 5 points 9 months ago* (last edited 9 months ago) (1 children)

Yes, I'm using the US international with dead keys layout. I also used it in Microsoft Windows. Here's a couple of annoying examples:

  • ' + c-> result: ć; expectation: ç
  • ' + m -> result: ḿ; expectation: 'm (particularly annoying when typing in english; workaround: ' + space key + m)
  • ' + t -> result: nothing happens; expectation: 't (particularly annoying when typing in english; workaround: ' + space key + t)

Right Alt + Comma does work for ç so at least I have that going for me. It's still weird to have a different layout for electron apps :/

[–] [email protected] 4 points 9 months ago* (last edited 9 months ago) (1 children)

You should be able to type ç the way I described for all apps, so you could just remove your custom layout. I highly recommend the English (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.

[–] [email protected] 2 points 9 months ago

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.

[–] [email protected] 3 points 9 months ago (1 children)

My situation is remarkably similar to yours down to the language, and I happen to have been considering a US keyboard as well so that's disheartening to hear. I have nothing to add right now but will let you know if I come across anything helpful!

[–] [email protected] 3 points 9 months ago* (last edited 9 months ago) (1 children)

I love US keyboards for coding, it really improves the experience. Typing in portuguese, however, is not a good experience. The default american layout has the ~ key in a really bad spot. Typing à or ã is REALLY uncomfortable/weird. Fortunately, my keyboard has that key on the right side of the keyboard instead of the left, which greatly improves the experience.

The .XCompose file I linked in the main post is perfect and works great on X11. If you're not yet on Wayland you can use it and have a great experience.

[–] [email protected] 2 points 9 months ago (1 children)

Right, that all makes sense. I'll definitely keep that .XCompose file in mind, wasn't aware it even was a thing before your post. Also, do you mind sharing the specific keyboard you're using for reference?

Side note, I've started using vim/helix a few months ago and the pt layout makes things a lot more awkward than I expected, that's half the reason I'm considering a US keyboard lol

[–] [email protected] 2 points 9 months ago (1 children)

I'm using an Happy Hacking Keyboard Professional 2. Not most people's cup of tea but I've grown used to it and it's hard for me to swap to anything else now :P

[–] [email protected] 1 points 9 months ago

I can see why it'd be divisive with topre keys, no key markings and a pretty non standard layout but man does it look nice. Really appreciate what they're going for there.

Anyway, thanks and hope you find a solution, I'll drop by if I come across anything useful!

[–] [email protected] 1 points 9 months ago* (last edited 9 months ago)

I'm very happy to report that I found a solution to the problem: keyd. It's amazing.

Instructions on the github project are crystal clear, but I'll leave some instructions below for Arch Users

yay -S keyd

sudo systemctl enable keyd && sudo systemctl start keyd

Now you can configure the /etc/keyd/default.conf file to your hearts desire. keyd is very feature rich, check the man page to see everything you can do. You can even add layers to your keyboard. Very sweet.

My personal configuration so far (I will definitely expand it later when I bump into more problems)

[ids]
*

[main]
' = oneshotm(apostrophe, ')

[apostrophe]
a = a
b = macro(space backspace apostrophe space b)
c = macro(backspace G-,)
d = macro(space backspace apostrophe space d)
e = e
f = macro(space backspace apostrophe space f)
g = macro(backspace apostrophe space g)
h = macro(space backspace apostrophe space h)
i = i
j = macro(space backspace apostrophe space j)
k = macro(backspace apostrophe space k)
l = macro(backspace apostrophe space l)
m = macro(backspace apostrophe space m)
n = macro(backspace apostrophe space n)
o = o
p = macro(space backspace apostrophe space p)
q = macro(space backspace apostrophe space q)
r = macro(backspace apostrophe space r)
s = macro(backspace apostrophe space s)
t = macro(backspace apostrophe space t)
u = u
v = macro(space backspace apostrophe space v)
w = macro(backspace apostrophe space w)
x = macro(space backspace apostrophe space x)
y = macro(backspace apostrophe space y)
z = macro(backspace apostrophe space z)

After editing /etc/keyd/default.conf make sure you run sudo keyd reload

[–] [email protected] 1 points 9 months ago (1 children)

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).

[–] [email protected] 1 points 9 months ago* (last edited 9 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