dotfiles VS river

Here's how to do it - in this example, I'm using my sway-menu python script to generate the menu itself. I'm also moving the menu to be near the cursor:

Maybe try my script sway-runner

As a geriatric user of sway, I don't always remember the keystrokes in the more esoteric corners of my configuration. I find that my script sway-menu helps with the bulk of the uncommon key bindings. But when I drop into a 'mode' (eg "move" mode) I don't always remember all the clever things I programed into it.

I wrote a simple bash script bluetooth-timeout to power-off the linux bluetooth stack after 10m of activity. Maybe this would help you.

Another source for ideas is to read through the configs and scripts written by others. I offer my own here - there are many others around.

sway-menu

Here's a script that uses nwg-wrapper to display a countdown - it would be easy to modify it to display a digital clock.

Imma gonna browse through your stuff to see if there's a scratch to a hitherto unnoticed itch that I can snarf. You might like to do the same with my dotfiles - particularly bin/sway-\, *.config/sway** and .config/waybar.

You might be able to modify my sway-next-empty-workspace script for that. Maybe see if changing swaymsg to i3-msg does the job.

I use myclipman to wrap clipman with wayland/swaywm to prevent passwords being cached.

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