I’d been running Wayland OK on my laptop for some months now, but I held off putting it on my main machine for one reason: when I logged into a Wayland session, Emacs would not recognize my Compose key (which I have set to Caps Lock). Today I finally figured out I have to install the “emacs-pgtk” package instead of “emacs-gtk”; the former is built with a version of GTK that works with Wayland. And yes, my Compose key works again. Still have to get used to slightly different input behaviour: previously, once I hit Compose, nothing would appear until I finished the whole key sequence. Now it echoes each keystroke immediately as I type it, in place, overwriting the previous echo (starting with an underline for the Compose key itself), then when I have typed the last key, it overwrites the echo area with the final character.
I’d been running Wayland OK on my laptop for some months now, but I held off putting it on my main machine for one reason: when I logged into a Wayland session, Emacs would not recognize my Compose key (which I have set to Caps Lock).
Today I finally figured out I have to install the “emacs-pgtk” package instead of “emacs-gtk”; the former is built with a version of GTK that works with Wayland. And yes, my Compose key works again.
Still have to get used to slightly different input behaviour: previously, once I hit Compose, nothing would appear until I finished the whole key sequence. Now it echoes each keystroke immediately as I type it, in place, overwriting the previous echo (starting with an underline for the Compose key itself), then when I have typed the last key, it overwrites the echo area with the final character.
Brave! :-) Any noticeable difference in performance? Faster refresh of windows, smoother dragging of windows? Cheers, Peter
On Wed, 24 Apr 2024 15:43:15 +1200, Peter Reutemann wrote:
Any noticeable difference in performance? Faster refresh of windows, smoother dragging of windows?
Not so much performance, but window-placement behaviour is slightly different. I think client apps under Wayland are not supposed to know, or care, where their windows are placed on the screen. I have one app that displays images; the window is initially sized according to the first image shown, then it dynamically resizes as necessary if it comes across a bigger one. Previously, the window would move as necessary on a resize to fit as much on screen as possible. Now it simply stays where it is, so you can end up with quie a lot of the display off the screen. And all the desktop effects still work, which is nice. By the way, if you want to know which GUI apps you are running are Wayland-native and which are still going through the X11 server, try running the “xeyes” program. This shows a pair of eyes that follow your mouse pointer, but it only works under X11. So if the mouse enters an X11 window, the eyes will track it; move to a Wayland-native window, and they won’t. And everything I am running right now seems to be Wayland-native: I had to find an old test X11 program I had written some years back just to confirm the xeyes trick does work. ;)
I have found one subtle difference in window behaviour. I am accustomed to having focus-follows-mouse set. This started failing, and then I noticed why: I now have to mouse into the content area of a window in order for it to take focus. Previously, mousing into the title bar would also work.
Another difference, this one on the bright side. My compose key never used to work in Blender before. But now it does! That means I can enter special characters directly into text fields, instead of copying/pasting from somewhere else.
Today I tried moving tabs between different KDE Konsole windows. This only works if the windows are all handled by the same Konsole process, which I have set, and which has worked before. But now I can only detach tabs into their own windows, not merge them back again. After a bit of searching, this seems to be confirmed as a Wayland-specific bug: <https://bugs.kde.org/show_bug.cgi?id=403324>.
On Wed, 24 Apr 2024 15:34:15 +1200, I wrote:
Today I finally figured out I have to install the “emacs-pgtk” package instead of “emacs-gtk”; the former is built with a version of GTK that works with Wayland. And yes, my Compose key works again.
Something else slightly odd: Emacs will not recognize the unmodified “/”, “*”, “-” and “+” keys on the numeric keypad as distinct from the alphanumeric ones. It still will with modifiers, except for some reason super-kp-subtract is not picked up at all. (Num Lock makes no difference to this behaviour.) I had a couple of those keys bound to custom commands. I have changed the key bindings to add some modifiers, for now.
participants (2)
-
Lawrence D'Oliveiro -
Peter Reutemann