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/
waleee has quit [Ping timeout: 268 seconds]
aryak has quit [Read error: Connection reset by peer]
aryak has joined #river
eShaev9z has joined #river
eShaev9z_ has quit [Ping timeout: 268 seconds]
snakedye has quit [Ping timeout: 255 seconds]
gbrlsnchs has quit [Quit: zzz]
talismanick has joined #river
fitrh has joined #river
fitrh has quit [Client Quit]
fitrh has joined #river
fitrh has quit [Quit: fitrh]
Ordoviz has joined #river
fitrh has joined #river
akumar[m] has joined #river
silv3r has joined #river
fitrh has quit [Read error: Connection reset by peer]
fitrh has joined #river
fitrh has quit [Read error: Connection reset by peer]
fitrh has joined #river
silv3r has quit [Quit: WeeChat 3.6]
notzmv has quit [Ping timeout: 268 seconds]
fitrh has quit [Quit: fitrh]
<tiosgz> i've noticed a weird behaviour with layer shell (specifically wofi)
smach has joined #river
<tiosgz> not sure if it's worth looking into for me rn, but i'm bored so it's possible
<tiosgz> if i spawn two wofis (which i do often to check my clipboard & primary histories), the "focused" view's border will only change after closing one of them
<tiosgz> in there, would it be expected to be the unfocused color immediately, or not at all?
<tiosgz> if i spawn two wofis and attempt to move focus to another output, the first wofi is still focused
<tiosgz> and only after closing it, the focus will switch to the other output (though it could take the other wofi first)
<tiosgz> in this case, is the expected behaviour that layer-shell takes precedence (focus switches after closing the second wofi)
<tiosgz> or that outputs take precedence (focus switches immediately, wofis get refocused when i enter that output again)?
notzmv has joined #river
<ifreund> tiosgz: just pushed a commit that I think should fixe that first issue with the border color not changing on focus change
<ifreund> As for the second, I think that the layer surface should take precedence even if it's on a different output
<ifreund> "output focus" is a concept specific to river and not part of the wayland protocol though so we can decide how it works
<tiosgz> whoa, you're too fast for me :D gonna check it out
<tiosgz> & thanks (for both)
<ifreund> I don't commonly use multiple keyboard-interactive layer surfaces at once, so I'm open to your input on what behavior is more convinient there
<ifreund> no problem! I hadn't noticed the border not changing and it turned out to be a bug I saw right away after opening up the code :)
<tiosgz> well, switching the output was a mistake actually (i thought the histories were empty so didn't expect any wofi to open)
<tiosgz> and it really depends on the perspective. though i think layer-shell precedence is more logical
<ifreund> yeah, I agree
<tiosgz> bugfix confirmed :)
<ifreund> :)
<uncomfyhalomacro> i saw stacktile written in zig, and i noticed it now uses `$XDG_CONFIG_HOME/stacktile/config.ini` as its configuration hmmm :D anyway me will wait until it gets fully rewritten
Ordoviz has quit [Ping timeout: 252 seconds]
Ordoviz has joined #river
waleee has joined #river
snakedye has joined #river
groknull has joined #river
groknull has quit [Remote host closed the connection]
snakedye has quit [Ping timeout: 252 seconds]
<leon-p> uncomfyhalomacro: did not have the time yet to write docs unfortunately :/
fitrh has joined #river
snakedye has joined #river
waleee has quit [Ping timeout: 248 seconds]
snakedye has quit [Ping timeout: 255 seconds]
snakedye has joined #river
snakedye has quit [Ping timeout: 260 seconds]
snakedye has joined #river
fitrh has quit [Quit: fitrh]
snakedye has quit [Ping timeout: 268 seconds]
smach has quit [Ping timeout: 260 seconds]
snakedye has joined #river
snakedye has quit [Ping timeout: 268 seconds]
snakedye has joined #river
waleee has joined #river
snakedye has quit [Ping timeout: 260 seconds]
snakedye has joined #river
snakedye has quit [Ping timeout: 268 seconds]
snakedye has joined #river
talismanick has quit [Ping timeout: 248 seconds]
snakedye has quit [Ping timeout: 252 seconds]
snakedye has joined #river
snakedye has quit [Ping timeout: 260 seconds]
snakedye has joined #river
Ordoviz has quit [Quit: WeeChat 3.6]
snakedye has quit [Ping timeout: 268 seconds]
talismanick has joined #river
snakedye has joined #river
talismanick has quit [Ping timeout: 244 seconds]
talismanick has joined #river
<talismanick> Anyone else have trouble with mic and video in Zoom from Firefox?
snakedye has quit [Ping timeout: 252 seconds]
snakedye has joined #river
snakedye has quit [Ping timeout: 260 seconds]
snakedye has joined #river
waleee has quit [Quit: WeeChat 3.6]
snakedye has quit [Ping timeout: 255 seconds]
snakedye has joined #river
nanospice has joined #river
snakedye has quit [Ping timeout: 252 seconds]
waleee has joined #river
<nanospice> I assume that if I'm trying to get river to work with EGLStreams, I am on my own?
nanospice has quit [Ping timeout: 252 seconds]
snakedye has joined #river
snakedye has quit [Ping timeout: 260 seconds]
snakedye has joined #river
eShaev9z_ has joined #river
ecocode____ has joined #river
notzmv has quit [*.net *.split]
eShaev9z has quit [*.net *.split]
ecocode___ has quit [*.net *.split]
Abdullah has quit [*.net *.split]
DemiMarie1 has quit [*.net *.split]
ecocode____ is now known as ecocode___
Abdullah has joined #river
DemiMarie1 has joined #river
Nosrep has joined #river
snakedye has quit [Ping timeout: 252 seconds]
snakedye has joined #river
<ifreund> talismanick: works fine for me... river doesn't touch those things fwiw
snakedye has quit [Ping timeout: 252 seconds]
<ifreund> or wait, what do you mean trouble with video?
<ifreund> like webcam?
<talismanick> yeah
<talismanick> Fair enough, I suppose that is the domain of wlroots
<ifreund> not wlroots either
<talismanick> (hardware support, rendering, etc)
<talismanick> wait, really?
<ifreund> firefox accesses the mic over pulseaudio or pipewire or whatever
<ifreund> not sure how it gets the webcam, but it's not over wayland
<talismanick> hm
<talismanick> ifreund: I only presumed as much because a new window pops up with the yellow microphone icon (which should be a small floating tile above FF)
<ifreund> I suppose the webcam is probably over pipewire or whatever pipewire is replacing with regards to video streams
<talismanick> Mm, yes, pipewire does handle more than audio, that's right
<talismanick> I forgot that
<talismanick> Bluetooth, etc
<ifreund> talismanick: that window is opened by firefox, river sees it the same as any other xdg-toplevel
<ifreund> (yes, it's pretty scuffed and firefox probably shouldn't do that)
<uncomfyhalomacro> <leon-p> "uncomfyhalomacro: did not have..." <- that window, i set it to floating because it does tile
<talismanick> Yeah, I was thinking about looking up how to disable it in about:config lol
<uncomfyhalomacro> wrong reply. my bad
<uncomfyhalomacro> talismanick: i think u cant or i just dunno.
<uncomfyhalomacro> sigh i shouldnt use reply. i forgot this is in IRC too
<talismanick> Matrix bridge? Anyways: yeah, I figured you probably can't, but if you can, it'll probably be in about:config
* talismanick engages in 2 minutes hate for Mozilla removing user customizability from FF