14:07 <dnkl> I'm testing the single-pixel buffer protocol, and it works. But, I'm not seeing any buffer-release events for it... is that expected?

14:20 <dnkl> guessing this is wlroots-related? Weston does emit release events

14:30 <dnkl> yeah, seems likely. Sway also does not release the buffers

14:49 <ifreund> dnkl: hmm, do you attach the single pixel buffer to multiple surfaces at the same time?

14:49 <ifreund> doing so makes everything about release events undefined iirc

14:49 <dnkl> ifreund: nope, but according to emersion it's best to consider it undefined anyway.

14:49 <ifreund> cool

14:50 <ifreund> ah, yeah I see the discussion in #wlroots now

14:50 <dnkl> yeah, ended up recreating them when I need them, and destroy immediately after commit

15:17 <AlmostSurelyRob> Hello,

15:17 <AlmostSurelyRob> I just made a plunge into river from Xmonad. I am particularly liking the tags. I am having though some stability issues and I was wondering if I can ask here if anyone had a similar problem. It looks like a segfault.

15:18 <AlmostSurelyRob> I could upload more data, but I thought I ask before. Maybe opening an issue would be a better way.

15:21 <ifreund> AlmostSurelyRob: what river version are you running? it may have already been fixed

15:21 <AlmostSurelyRob> Oh, that's a good point. I am on Fedora 39, so I just used the one from repos. Are you suggesting I should compile from source?

15:22 <ifreund> what's `river -version` say?

15:22 <AlmostSurelyRob> Yes, I was just checking 0.2.1.

15:23 <ifreund> 0.2.1 is very old, the lastest version is 0.3.2

15:23 <AlmostSurelyRob> Ok. I will update first.

15:23 <ifreund> So, yeah I'd suggest compiling a newer version from source if that's all fedora offers

15:33 <AlmostSurelyRob> I guess I also need to get more up to date zig as Fedora comes with 0.9.1?

15:44 <gbrlsnchs> hi folks, qq: when focusing another output, is there a way to force the mouse pointer to also go to that output without having to move it manually there?

15:45 <gbrlsnchs> the context is, I'm using a virtual output and its position is, like, 9999,9999, so that I don't accidentally move my mouse to it, but it's still usable for screen sharing, etc

15:47 <AlmostSurelyRob> Is this what `set-cursor-warp` does in `riverctl`? There seem to be several options for it.

15:48 <AlmostSurelyRob> (I haven't tested it myself yet)

15:49 <gbrlsnchs> AlmostSurelyRob: ahhh, perfect! I have totally missed it while reading the man page... thank you!

15:49 <AlmostSurelyRob> I am very fresh from reading man pages so no worries.

15:50 <gbrlsnchs> In fact, `riverctl set-cursor-warp on-output-change` is what I was looking for

16:15 <AlmostSurelyRob> Quick question too. Just recompiled 0.3.2 and placed in `~/apps/os/river`, but I now have Fedora package in /usr and my own. What's a good way to avoid collision? Should I completely uninstall river from repos and then build install into usr?

16:17 <ifreund> AlmostSurelyRob: I personally prefer to install stuff I build my self to ~/.local rather than /usr and place e.g. ~/.local/bin ahead of /usr/bin in my path

16:17 <ifreund> this pretty much comes down to personal preference though, there is no one "right" way

16:22 <AlmostSurelyRob> Sorry, this is the piece I don't quite get in general Linux. I normally modify my PATH in a session of zsh/bash, but I need something system wide here, right? So is that the case of editing /etc/environment or /etc/profile?

16:23 <ifreund> how are you launching river? you'd need to set it in something that gets run before river is launched

16:23 <ifreund> e.g. I launch river from my .zshprofile and set $PATH from the same

16:30 <AlmostSurelyRob> Oh, wait I think it just dawned on me. I am pursuing an ultimate consistency and it's not really necessary...

16:30 <AlmostSurelyRob> I could just add path to my shell and proceed as normal.

16:30 <AlmostSurelyRob> But I launch it via a desktop entry in ~/.config/wayland-session/river.desktop, which points to a wrapper and that then points to my installation in HOME.

16:30 <AlmostSurelyRob> So this way it would just work fine.