ifreund changed the topic of #river to: river - a dynamic tiling wayland compositor || https://github.com/ifreund/river || channel logs: https://libera.irclog.whitequark.org/river/
yyp has quit [Read error: Connection reset by peer]
yyp has joined #river
waleee has quit [Ping timeout: 260 seconds]
snakedye has quit [Ping timeout: 260 seconds]
leon-p has quit [Ping timeout: 245 seconds]
yyp has quit [Read error: Connection reset by peer]
yyp has joined #river
emersion has quit [Read error: Connection reset by peer]
emersion has joined #river
ecocode__ has quit [Ping timeout: 264 seconds]
ecocode__ has joined #river
novakane has joined #river
leon-p has joined #river
snakedye has joined #river
kindablue has quit [Ping timeout: 260 seconds]
waleee has joined #river
kindablue has joined #river
waleee has quit [Ping timeout: 264 seconds]
crypt_ has quit [Ping timeout: 258 seconds]
snakedye has quit [Ping timeout: 264 seconds]
snakedye has joined #river
ext0l has quit [Ping timeout: 260 seconds]
snakedye has quit [Ping timeout: 260 seconds]
snakedye has joined #river
snakedye has quit [Ping timeout: 260 seconds]
adelaide has joined #river
kindablue has quit [Quit: System Rebooting..]
kindablue has joined #river
adelaide has left #river [#river]
yyp has quit [Read error: Connection reset by peer]
yyp has joined #river
adelaide has joined #river
<adelaide> Is there a utility similar to sway's grimshot for river somewhere?
<dnkl> I just use a key binding for slurp+grim...
<novakane> I use a shell script for slurp+grim https://git.sr.ht/~novakane/bin/tree/main/item/snap
<adelaide> welp
<adelaide> It seems I can already use grimshot directly for entire screen and selection
<adelaide> It's active output and active window capturing, which I do use regularly, that don't work
<adelaide> since they use swaymsg
<adelaide> Is the equivalent of those functionalities supported in river?
<leon-p> it is not yet possible to querry the position and dimensions of the active window and I am not sure if it ever will be. Basically we want to keep the amount of information river grants clients as small as possible to not repeat one of Xs major mistakes
<msiedlaczekelshi> is anyone running gnome-keyring in river? I'm having some issues when not logging in via gdm but rather running river from tty. the keyring daemon is running but it's locked. I tried manually unlocking it with seahorse, but it just doesn't react at all... I don't really know what I'm doing here so I'd appreciate it if someone has any experience to share.
<ifreund> leon-p: it might be possible as part of the hypothetical river-window-manager client depending on how that protocol shapes up
<ifreund> probably this should be solved in a general way that is portable between compositors though
<ifreund> i.e. something based on ext-toplevel-info
leon-p has quit [Quit: leon-p]
adelaide has left #river [#river]
snakedye has joined #river
snakedye has quit [Ping timeout: 258 seconds]
snakedye has joined #river
doaN[m] has joined #river
snakedye has quit [Read error: Connection reset by peer]
snakedye has joined #river
waleee has joined #river
novakane has quit [Quit: WeeChat 3.3]
crypt_ has joined #river
snakedye has quit [Ping timeout: 264 seconds]
snakedye has joined #river
leon-p has joined #river
snakedye has quit [Ping timeout: 268 seconds]
snakedye has joined #river