ifreund changed the topic of #river to: river - a dynamic tiling wayland compositor || https://github.com/riverwm/river || channel logs: https://libera.irclog.whitequark.org/river/
kotto has quit [Quit: WeeChat 4.0.2]
waleee has quit [Ping timeout: 244 seconds]
jao has quit [Ping timeout: 245 seconds]
eShaev9z has joined #river
eShaev9z_ has quit [Ping timeout: 264 seconds]
nevoyu has joined #river
<nevoyu> So whats the status on the next river release so I can make use to the tag rules that were added recently?
angry_vincent has joined #river
notzmv has joined #river
leopoldek has quit [Ping timeout: 246 seconds]
Guest45 has joined #river
Guest45 has quit [Client Quit]
<ifreund> nevoyu: it will happen when all the known bugs are fixed as well as the things I put in the 0.3.0 milestone on the issue tracker
<ifreund> the blocker is me having time, probably late August at the earliest
<ifreund> September may be more realistic
nevoyu has quit [Remote host closed the connection]
waleee has joined #river
kotto has joined #river
waleee has quit [Ping timeout: 244 seconds]
jao has joined #river
047AAAWNB has quit [Ping timeout: 260 seconds]
aryak_ has joined #river
notzmv has quit [Ping timeout: 264 seconds]
waleee has joined #river
kotto has quit [Quit: WeeChat 4.0.2]
leopoldek has joined #river
leopoldek has quit [Ping timeout: 260 seconds]
notzmv has joined #river
chris3 has quit [Remote host closed the connection]
chris3 has joined #river
leopoldek has joined #river
leopoldek has quit [Ping timeout: 246 seconds]
notzmv has quit [Ping timeout: 260 seconds]
angry_vincent has quit [Remote host closed the connection]
waleee has quit [Ping timeout: 245 seconds]
waleee has joined #river
chris3 has quit [Remote host closed the connection]
chris3 has joined #river
chris3 has quit [Remote host closed the connection]
chris3 has joined #river
waleee has quit [Ping timeout: 264 seconds]
notzmv has joined #river
waleee has joined #river
leopoldek has joined #river
jjjjj has joined #river
Nosrep has quit [Remote host closed the connection]
Nosrep has joined #river
<Nosrep> any idea why obs/pipewire screen recording just dies when kernel updates without a reboot (arch)
<Nosrep> complains about "couldn't create pipewire context"
jao has quit [Ping timeout: 244 seconds]