xmonad
Wayland support
There is an old closed issue of https://github.com/xmonad/xmonad/issues/38 but recently Red Hat announced it will stop developing X.org, so switch to Wayland is inevitable.
https://blogs.gnome.org/uraeus/2019/06/24/on-the-road-to-fedora-workstation-31/
Never going to happen for XMonad. As the name suggests it is very tightly coupled to x.org/x11. The whole concept of a separate window manage is really going away with Wayland anyway. The compositor and window manager are the same thing in most Wayland impls. You can check out waymonad for a haskell based Wayland compositor.
"X Clients under Wayland (XWayland)" https://wayland.freedesktop.org/xserver.html
This only allows X11 programs/clients to run under Wayland; it doesn't enable an X11 window manager to manage Wayland windows, including those of X11 programs.
On Tue, Sep 15, 2020 at 3:52 PM Jeremy Barisch-Rooney < [email protected]> wrote:
https://wayland.freedesktop.org/xserver.html
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/xmonad/xmonad/issues/193#issuecomment-692942800, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAPRFICDSKLO66HZHK4SWT3SF7AXNANCNFSM4H4JUSEA .
-- brandon s allbery kf8nh [email protected]
@crocket Waymonad looks dead/abandoned. Patching Xmonad is the only way it seems.
I heard that library support for implementing wayland (e.g. wlroots) has dramatically improved in the recent days. There was even reports of a person making a wayland compositor in weeks. It might even be feasible to implement wayland-xmonad for the xmonad teams with minimal assistance.
Wouldn't this change any matter on xmonad on wayland / Waymonad?
@Abastro wlroots and the wider wayland ecosystem maturing certainly does make it more feasible to start experimenting with xmonad+wayland. There are other issues, unfortunately.
As others mentioned before, a port of xmonad to Wayland where old configs still work is fundamentally impossible. Therefore whatever comes out of this effort would inevitably be a slightly different window manager/compositor, inspired by xmonad. There are conflicting opinions within the community about what actually makes xmonad be xmonad, so the degree of similarity to good old xmonad will largely depend on who ends up doing the work.
Speaking of doing the work, the current team is still extremely busy just maintaining the X11 version: dealing with bug reports and reviewing pull requests that keep coming. And there's also life and day jobs and other stuff that affect the amount of free time we can devote to xmonad. Personally I agree the time is nigh to start doing Wayland-ey stuff, but I've burned myself out working full time with no income on xmonad and other open-source stuff in 2020/2021, and now I need to catch up with the realities of life, so I won't be involved with this any time soon.
I'm still of the opinion that we'll have to invest some of our OC money in paying someone with more Wayland clue to write it. It at least seems more possible now, as parts of the Wayland ecosystem start to mature.
Hi, I'm a big Xmonad enthusiast user, and I'm really concerned about its future, along the Wayland's coming over Xorg. Waymonad seems quite an alpha that will miss lots of Xmonad functionalities, at the current point. I've not the technical knowledge about to suggest a solution for made Xmonad usable using Xwayland.
But today I saw this video by Brodie Robertson
https://www.youtube.com/watch?v=8jmxhhdfSd8
I wonder if this could be used to made xmonad usable under Xwayland
Since this issue is still open, I ask here this question, hoping that this could be a good point
Recent discussion here: https://discourse.haskell.org/t/xmonad-for-wayland-call-for-help
Xmonad is very stable and I like it very much. I hope he can support wayland
