thanks! kinda, but i’m using hyprland and the foot terminal. You can control the inactive opacity on hyprland, and control foot’s alpha channel, which can make it transparent
No problem! My first switch to Wayland was with Hyprland. It’s very fancy and I see how this tool can get along with it quite nicely. Though I was a Bspwm user and switched to River recently. I usually only see my wallpaper when I first boot the system and if I want to run a non-automated program. But still even for me this can be useful when I work with two monitors.
Would this run on River by the way? Since River handles workspaces a little differently.
I searched for a River socket or riverctl command that would allow me to get the active workspace number, but i couldn’t find a way for that currently in River. so i can’t implement it for River not currently at least. unless maybe someone knows a way to get that info who could refer me to the documentation
thanks! kinda, but i’m using hyprland and the foot terminal. You can control the inactive opacity on hyprland, and control foot’s alpha channel, which can make it transparent
No problem! My first switch to Wayland was with Hyprland. It’s very fancy and I see how this tool can get along with it quite nicely. Though I was a Bspwm user and switched to River recently. I usually only see my wallpaper when I first boot the system and if I want to run a non-automated program. But still even for me this can be useful when I work with two monitors.
Would this run on River by the way? Since River handles workspaces a little differently.
very fancy and nice to use. i see
I searched for a River socket or riverctl command that would allow me to get the active workspace number, but i couldn’t find a way for that currently in River. so i can’t implement it for River not currently at least. unless maybe someone knows a way to get that info who could refer me to the documentation