leftwm VS river

(Also I wouldn't mind if you want to contribute to leftwm ;))

LeftWM if you are adventurous and want to support more Rust projects on Linux.

I'm using a tiling window manager (LeftWM) and picom with experimental backends for compositing. I'm running into issues configuring picom for use on my laptop when I am on battery power. Two problems arise:

I've looked at these: - DWM: A popular, compact WM written in C - LeftWM: A popular, configurable WM written in Rust - GabelstaplerWM: An obscure, compact WM written in Rust - XCB DWM: An abandoned rewrite of DWM using XCB

Been using and liking LeftWM: https://github.com/leftwm/leftwm

In particular, I think that "ultrawide-vertical-stack" (based on "CenterMain" from LeftWM) is quite close to what you are looking for. Give it a try with komorebic change-layout ultrawide-vertical-stack!

Once again I'm happy to answer any questions, and I want to give a special thanks to nog, leftwm and umberwm, whose work this project borrows from and builds upon.

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