cagebreak VS cage

There's also a Wayland WM directly inspired by ratpoison! https://github.com/project-repo/cagebreak

That's true for a lot of libraries, you have to maintain the code, I would treat that as a fact of life, It might be worth noting there are some projects designed to provide a high level abstraction over wlroots which might be different: cage -> used by cagebreak phoc -> used by phosh and wayfire -> used by swayfire.

cagebreak as far as i can tell is a one man project (it uses cage to provide a high level abstraction over wlroots).

I also remembered cagebreak (wayland window manager). it uses cage (which is defined as a "wayland kiosk" but might also be used as a high level abstraction over wlroots).

Anyway, like you I also wanted to see how far I could go on Wayland. After trying out a number of wms I settled on cagebreak which is modeled on ratpoison. It's still in early development but worked well enough for me to give it a semi daily driver status. It works really well with emacs too, without the single-thread issue. I went for a pure Wayland experience (without XWayland as well), so I couldn't some apps I normally use - but I was able to create something quite close to my xorg setup.

There's cagebreak, wich is inspired by ratpoison. It's different yo hlwm, but it has the same concept of containers, but every container only have the "max" layout

You... might be able to, kind of, depending on your goal... So the thing is, if all you need is a single screen (or at least, I've not run this multi-monitor) and you're just working around drivers that don't support Xorg, you can just run cage ( https://github.com/cage-kiosk/cage ), run xwayland on that, and run your real GUI on that. Of course, then you're skipping all the advantages of wayland except hardware/driver compatibility.

For "real" wayland, sibling comments are correct that you'd need a wayland compositor that reimplemented awesome.

> As a developer, I needed to port a custom Linux system to hardware that only has Wayland drivers and it was a giant pain. Wayland offers no advantage at all for that system but it broke a lot of functionality that relied on X in terms of window placement, etc.

FWIW, I've had decent luck running cage ( https://www.hjdskes.nl/projects/cage/ ), then on that xwayland, and then just ignoring wayland and running X clients. The result does still have some slight quirks, but it mostly works fine.

That did help me find https://github.com/cage-kiosk/cage/wiki initially I'm here there's other going down that path. Thanks

I thought this was going to be some development news with Wayland compositing going further: https://emacsconf.org/2022/talks/wayland/. Maybe it's because 29.1 was on my mind with the full Wayland client support being released.

If you want to just run one application in a modern way (yes, I'm assuming you agree that Wayland is desirable), then check out https://www.hjdskes.nl/projects/cage/.

You can run Wayland inside Xorg via cage[1] so you don't need to use a Wayland compositor.

[1]: https://github.com/cage-kiosk/cage

Just ran into cage, seems useful.

It's kiosk mode. Sometimes related to POS. You can use https://github.com/cage-kiosk/cage (Wayland) for example.

Maybe starting with reimplementing something like this: https://github.com/cage-kiosk/cage would be the easiest?