EXWM and Wayland

So, one evening I was messing around trying to find a suitable compositor to switch from EXWM to <insert compositor>, but found nothing really appealing. However, I've stumbled upon Cage and I've got a curious question - will it suffice as a Wayland bootloader for an EXWM session with XWayland turned on? I'm sorry if all of this sounds cryptic, I was just wondering whether anyone tried to do the same (e. g. launching an EXWM session withing a Wayland kiosk). INB4 any experiences and input are appreciated!

Why? I used EXWM in X. But decided to switch to wayland and Sway. Works perfectly for my workflow.

I don't like an idea of switching and configuring another window manager. Also, the question was whether it is possible at all to do so.

I suppose that’s as good reason as any. But why not stick to X if that workflow works for you?

Sway doesn't have anything like exwm-simulation-keys does it? That feature is 100% indispensable for me; I could never imagine using a system without it.

I got this running using Cage on my MNT Reform system, which has a weird GPU that does not support xorg. It's extremely hacky and gives lots of visual glitches all the time. That said, even with the glitches it's much better than running a wayland WM that doesn't have simulation keys. But if you do have the option to use xorg you should! It's much, much better.

No. But there are solutions (which I haven’t used my self). See: https://github.com/acro5piano/wayremap. Edit: found this: https://github.com/k0kubun/xremap

No particular reason but making my setup future-proof and expanding my view of various possibilities. Also, this might solve a weird glitch which I have on EXWM startup (when it tries to resize itself to fit the whole screen).

Got it.

What do you need Wayland _for_? To answer your question, no it's probably not possible or if it is it will be a lot of work; but the xandyproblem is what does Wayland give you that you _need_? X won't go anywhere or be any less stable, apps will still primarily support X. You're setting yourself up for _a lot_ of headache for very little gain.

Different scaling by monitor when having hidpi monitor and hd monitor

It's not about Wayland, but rather using EXWM in Cage. I'm not planning to ditch X anytime soon.

I would argue that X is on its way to being replaced for good ... but then, that's what I said ten years ago. So in conclusion, X isn't going anywhere.

And that's worth dropping X completely and dealing with all the issues regularly yourself regularly?

I've read that X should be a part of any Wayland compositor, so it will never of away indeed.

I've been using Sway once for a long while and haven't encountered any issues. In my defence, I have an ATI card.

Not directly Wayland issues, EXWM <=> Wayland issues.

X is future-proof, it's not going anywhere and is still being worked on. None of us will likely be alive by the time Wayland does ever replace X.

It is not actively developed and the majority of the manpower if working on Wayland and XWayland respectively.

Well I moved from x to Wayland for that particular reason. I know there are issues, but they are not 'no-gos' in my opinion. Also I know they one day will be solved, but x won't solve multiple monitor scaling.

I recall reading ch11ng, the author of EXWM, say that EXWM won't work on Wayland (for some technical reasons that I can't remember). 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](https://github.com/project-repo/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 run some apps I normally use - but I was able to create something quite close to my xorg setup.