00:12 <NickH> FYI I've been keeping my Zig and River debian packages up to date. There is some progress getting Zig into Debian and once that's in, River shouldn't be too far behind.

06:41 <ifreund> neato :)

06:42 <ifreund> daurnimator: I'm not planning on tagging releases for zig-wayland and company until the zig package manager is far enough along that I can switch away from submodules

08:26 <p00f1> andrea: i thought the maintainer pulled river from aur because i flagged it out of date when 0.2.3 was released 😭

10:19 <ifreund> of course there already another bug fix commit on master that wasn't included in 0.2.3 :/

10:19 <ifreund> well, I'll probably do an 0.2.4 after another 2 weeks or something I guess

10:42 <andrea> p00f1: hahaha no, I even managed to update the package just before it was deleted :)

10:43 <ifreund> heh :D

12:55 <EmoSpice> Hello! I have a small nit with 0.1.3 and multiple displays. When plugged into an external monitor, my mouse pointer becomes "locked" to a single output and cannot seemingly be moved.

12:56 <EmoSpice> I know that 0.1.3 is not latest, but I'm mostly curious if this is known to have a workaround or a fix in later versions.

13:00 <ifreund> EmoSpice: if you configure your displays to not be directly adjacent you won't be able to move the mouse between them

13:02 <EmoSpice> What does "directly adjacent" mean here? My kanshi config sets up external monitor to be exactly offset from the width of the internal one: internal is 3200x1800. external position is 3200x0

13:02 <EmoSpice> (i am asking for clarification to make sure I'm not somehow off-by-one or somthing...)

13:03 <ifreund> could you drop the output of wlr-randr in a pastebin or something so I can see exactly what your config is?

13:05 <EmoSpice> Of course.

13:07 <EmoSpice> http://ix.io/4m5m

13:08 <ifreund> EmoSpice: I believe you want your second monitor at 1600,0 since the scale of the first is 2x

13:08 <ifreund> note that there are GUI clients such as wdisplays that would show this graphically

13:09 <EmoSpice> Can I blame lack of coffee if this has been broken for days?

13:09 <ifreund> Of course :)

13:11 <EmoSpice> That does - of course - work.

13:11 <EmoSpice> I've left a reminder note that these are scale-dependent points and not pixel offsets...

13:13 <ifreund> They're "logical pixels" in the compositor's coordinate system, a 3200x1800 output at 2x scale is seen by the compositor as 1600x900 logical pixels for the purposes of aligning windows, rendering, etc

13:15 <EmoSpice> That's a better term for them. I'll drop that in my config instead!

14:34 <p00f1> would it work if they moved their mouse more or no

14:34 <ifreund> p00f1: nope, cursors are kept in bounds of the output layout, other wise it would be pretty easy to lose your mouse

14:50 <p00f1> ah

18:24 <leon-p> it probably is possible to cross small "gaps" by moving fast enough, since IIRC it works with deltas, but that is not really an intended feature

21:07 <kraem_> ifreund: somehow i wasn't able to recreate the crash but it just happened again and i have the debug symbols. i'll send them over tomorrow :)