river VS dwm-flexipatch

More info on the wiki https://github.com/riverwm/river/wiki

Here is the related github issue

If you can get past some minor wayland related annoyances, river is pretty easy imo, you can write a config in whatever format you want, it just needs to be an executable file, the most common type is a shell script. The actual configuration happens by calling the riverctl program from the file, which from what I've heard is a similar method compared to bspwm.

Coming from awesome you may find river more to your liking than sway.

River crashed everytime I closed Chromium. The developer fixed it in 5 minutes :)

I've written a plugin that implements the river-layout-v3 wayland protocol in Hyprland. This means you can run something like rivertile, river-luatile, rivercarro or kile as a layout provider.

Author here. And yeah, as of 0.6.0 it supports master stack - I just called it stack main. I was in fact inspired by river: https://github.com/riverwm/river. River is really promising but is still in very early development. Sway on the other hand has been around for a long time and I, for now, prefer that stability.

In my very specific case, I'd probably start by taking a look at how animations were previously implemented in river, and then I'd pay careful attention to that transform matrix at the end. I'm not super crazy about the implementation using timers to drive it (versus interpolating where the transform should be across a deadline), but I guess they were going for smoothness.

riverwm wayland compositor

However, if I were to implement something like 15+ patches then i would just use flexi patch to quickly apply patches - https://github.com/bakkeby/dwm-flexipatch.

I posted an issue with flexipatch's savefloats patch https://github.com/bakkeby/dwm-flexipatch/issues/362 which I believe to be a bug in the way the patch is supposed to handle layout switching.

Check out dwm-flexipatch!

And if you want a quick way to install patches then you should checkout u/bakkeby 's https://github.com/bakkeby/dwm-flexipatch.

do yourself a favor and use https://github.com/bakkeby/dwm-flexipatch ... patching with much less trouble

and i would recommend to use dwm-flexipatch, it makes the hole patching process very easy, and you can try out all the patches...

I just wanted to add that if anyone is experiencing this issue and using dwm-flexipatch then enabling the patch BAR_NO_COLOR_EMOJI_PATCH may solve the issue.

if your not scared of changing basic C files the most lightweight you’ll get is probably dwm, try out this to more easily patch dwm if you do decide to use it.

a lot of functionality can be added with patches, but you have to try and juggle those all yourself (and work out any conflicts between them yourself) - there are some projects like dwm-flexipatch to try and make it easier to deal with them, but it's way more trouble than I am interested in