> Wayland is still feature incomplete. Thats intended, Wayland was invented to drop old historic parts of X11, but maybe it dropped too much at the start.
> The number of distributions supporting X11 hasn't dwindled to a mere handful > yet. No distro is going to "not support X11" any time soon, thats what XWayland is for. Where the problem comes is that if the Geany packaged by the distro defaults to running on Wayland then X11 events won't be received, so that Geanylua code won't work, or even worse will attempt to interpret a Wayland event as an X11 event. And Wayland by default is increasing, Ubuntu 22.04 is Wayland by default IIUC, Fedora has been for a while, Debian Gnome since Debian 10 IIUC. > Are there any other X11 issues besides the key event hooks? AFACGSCT no (As Far As Crappy Github Search Can Tell ;-) > LuaJIT seems to be the most expedient path. If its only a build change then basically I agree. But the X11 problem still remains, I will open a separate issue for that. @hyperair how do we make sure packagers are aware that the dependency of a plugin changed? -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/issues/1133#issuecomment-1454338608 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany-plugins/issues/1133/[email protected]>
