ifreund changed the topic of #river to: river - a dynamic tiling wayland compositor - https://github.com/ifreund/river - channel logs: https://freenode.irclog.whitequark.org/river/
dominikh has quit [Ping timeout: 264 seconds]
_whitelogger has joined #river
dominikh has joined #river
dominikh is now known as Guest25657
st4ll1 has quit [Quit: WeeChat 2.9]
skuzzymiglet has quit [Ping timeout: 240 seconds]
betawaffle has quit [Ping timeout: 240 seconds]
skuzzymiglet has joined #river
betawaffle has joined #river
leon-p has quit [Remote host closed the connection]
leon-p has joined #river
waleee-cl has quit [Quit: Connection closed for inactivity]
leon-p has quit [Quit: leaving]
yyp has joined #river
yyp has quit [Quit: disconnected]
_whitelogger has joined #river
anthony25 has quit [Quit: Quitte]
anthony25 has joined #river
Guest25657 is now known as dominikh
gspe has joined #river
waleee-cl has joined #river
<skuzzymiglet> ifreund: I've heard river was your first project in Zig, had you worked on window managers before?
<ifreund> skuzzymiglet: nope! all I'd done with wayland before river was write a screenlocker and patch one bug in wlroots I found annoying
<ifreund> never did anything significant with X11, looked at it briefly which is what inspired me to switch to wayland/sway in the first place
<skuzzymiglet> you were familiar with wlroot though, right?
<skuzzymiglet> s/root/roots
<ifreund> not really, I'd never looked at its code before I patched that bug
<ifreund> and didn't look at it again until I started working on river
<skuzzymiglet> when I open fuzzel, river aborts
<skuzzymiglet> both directly and through the keybinding
<skuzzymiglet> it only seems to happen when I have a second hdmi screen attached
<skuzzymiglet> and it doesn't matter what screen I launch it on
<ifreund> hrm, fuzzel aborts when run in a nested session...
<skuzzymiglet> nested session?
<ifreund> running river inside river
<skuzzymiglet> so when you connect another display, is it it's own compositor?
<ifreund> dnkl: opened a fuzzel issue for you with a stack trace :)
<dnkl> ifreund: skuzzymiglet: let me know if there's anything I can help wit.... and there I got the mail
<dnkl> 😂
<skuzzymiglet> man I love when bugs are that easy to reproduce
<ifreund> skuzzymiglet: no, a completely separate river session run using wlroots' wayland backend
<ifreund> which is very useful for testing bugs involving multiple outputs on a machine with only a single monitor
<dnkl> Looks like fuzzel doesn't get output info. Something with the wl_output interface?
<ifreund> looks like wlroots is sending 0 width and heigth in wl_output.geometry
<ifreund> foot seems to handle it fine though
<dnkl> Foot might have better fallback handling...
<ifreund> WAYLAND_DEBUG log: https://0x0.st/-8z9.txt
<dnkl> On the phone right now, but will fix the crash in fuzzel latef
<ifreund> much appreciated :)
leon-p has joined #river
yyp has joined #river
yyp has quit [Quit: have a great day]
yyp has joined #river
yyp has quit [Quit: disconnected]
yyp has joined #river
gspe has quit [Quit: gspe]
gspe has joined #river
<leon-p> Do we explicitly close layer surfaces before disabling an output? Sway does and I was wondering about whether other compositors do the same or just let the layer shell client destroy the surface themselves.
<yyp> I think we should
<leon-p> based on what?
<yyp> What if a client messes up with a heavy surface not destroying it - that's a memory leak
<skuzzymiglet> skimming the source it seems river does
<skuzzymiglet> disclaimer: I haven't read the source before :)
<leon-p> yyp: generally a compositor should not workaround client bugs
<leon-p> skuzzymiglet: thanks, probably should have done that in the first place :)
<leon-p> I'll have to re-read the protocol again, because I wonder if it explicitly enforces this.
<ifreund> yes we do, which is the right thing to do
<skuzzymiglet> ripgrep is really good for that type of thing
<skuzzymiglet> I regularly run it on the void-packages repo and it's pretty damn fast
<skuzzymiglet> is `error.SeatNotAdverstised` a typo?
<yyp> I don't think so
<skuzzymiglet> adverstised?
<skuzzymiglet> does it mean something different to advertised?
<ifreund> yes that's a typo
yyp has quit [Quit: disconnected]
gspe has quit [Quit: gspe]