I got my Nvidia GPU before I even considered moving to Linux. I am honestly getting pretty tired of reading these gatekeeping comments telling me “I’m not allowed to complain about anything” or how I’m a trash person for buying an Nvidia card in the first place. Nvidia is the largest GPU manufacter, people are going to own Nvidia cards, you need to live with it. Be constructive and nice to other people.
X11 is rock solid with Nvidia, never had a single problem.
I had a lot of issues with Wayland on KDE, lots of flickering issues all the time. I moved to Hyprland and things are mostly fine. IntelliJ has ocasional problems but they are working on a Wayland version anyways.
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)
<span style="color:#323232;">[ids]
</span><span style="color:#323232;">*
</span><span style="color:#323232;">
</span><span style="color:#323232;">[main]
</span><span style="color:#323232;">' = oneshotm(apostrophe, ')
</span><span style="color:#323232;">
</span><span style="color:#323232;">[apostrophe]
</span><span style="color:#323232;">a = a
</span><span style="color:#323232;">b = macro(space backspace apostrophe space b)
</span><span style="color:#323232;">c = macro(backspace G-,)
</span><span style="color:#323232;">d = macro(space backspace apostrophe space d)
</span><span style="color:#323232;">e = e
</span><span style="color:#323232;">f = macro(space backspace apostrophe space f)
</span><span style="color:#323232;">g = macro(backspace apostrophe space g)
</span><span style="color:#323232;">h = macro(space backspace apostrophe space h)
</span><span style="color:#323232;">i = i
</span><span style="color:#323232;">j = macro(space backspace apostrophe space j)
</span><span style="color:#323232;">k = macro(backspace apostrophe space k)
</span><span style="color:#323232;">l = macro(backspace apostrophe space l)
</span><span style="color:#323232;">m = macro(backspace apostrophe space m)
</span><span style="color:#323232;">n = macro(backspace apostrophe space n)
</span><span style="color:#323232;">o = o
</span><span style="color:#323232;">p = macro(space backspace apostrophe space p)
</span><span style="color:#323232;">q = macro(space backspace apostrophe space q)
</span><span style="color:#323232;">r = macro(backspace apostrophe space r)
</span><span style="color:#323232;">s = macro(backspace apostrophe space s)
</span><span style="color:#323232;">t = macro(backspace apostrophe space t)
</span><span style="color:#323232;">u = u
</span><span style="color:#323232;">v = macro(space backspace apostrophe space v)
</span><span style="color:#323232;">w = macro(backspace apostrophe space w)
</span><span style="color:#323232;">x = macro(space backspace apostrophe space x)
</span><span style="color:#323232;">y = macro(backspace apostrophe space y)
</span><span style="color:#323232;">z = macro(backspace apostrophe space z)
</span><span style="color:#323232;">
</span>
After editing /etc/keyd/default.conf make sure you run sudo keyd reload
I had to set a ton more. Without the ozone flags my electron apps flicker and have this sync problem that appears to eat letters while I type them. Different electron apps use different configuration files, it’s a mess.
I wouldn’t consider my setup to be complex enough for the amount of trouble I had to make the system work under Wayland.
I’m using an Nvidia GPU, I’m sure things would be more streamlined if I had something else.
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
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.
I think the main problem is that Wayland is not a drop in replacement.
Every software needs to support Wayland, new environment flags need to be created, flags must be used with electron apps…
Nvidia support has been spotty and some functionality has not yet been implemented. I use a custom .xcompose file, which doesn’t work on electron apps. Let me know if there’s a better way to mimic window’s dead keys.
Overall, it’s hard for an end user to change from a solution that is working perfectly to a solution that requires a ton of work and doesn’t yet have the same functionality.
Everyone can understand that Wayland is the future but depending on your needs and hardware the current experience can be great or terrible.