04:32 <LarstiQ> JustineSmithies: I believe that would need https://gitlab.freedesktop.org/wlroots/wlroots/-/merge_requests/4543

04:32 <LarstiQ> and then a river implementation

10:07 <ifreund> foreign-toplevel-list is unrelated to mapping tags to window app-id/title

10:08 <ifreund> and yeah, river doesn't expose a way to access this information yet

10:46 <ifreund> TIL, `man -Thtml` is a thing

10:46 <ifreund> guess my new website will also host river man pages for the latest river release

11:05 <ifreund> actually, this seems like a fair bit of effort to do well and annoying to keep up to date

11:09 <LarstiQ> ifreund: ah, I confused it with the stable identifier for a toplevel maybe. Not sure now what I was thinking

11:18 <LarstiQ> right, this is what my memory latched onto: https://libera.irclog.whitequark.org/river/2023-11-25#35301024;

11:23 <ifreund> My current plan is to not do that and just work on the window management protocol instead fwiw

11:24 <ifreund> which will make the compositor process unaware of tags and unable to link them to foreign-toplevel-list objects

12:12 <LarstiQ> but then clients via the window management protocol could do that, right?

12:15 <ifreund> LarstiQ: well, only the single window manager client but it could expose the information to other tools as it chooses

12:22 <leon-p> I think we should still implement the foreign toplevel stuff since a lot of external utilities will make use of that. River could then merely propagate f.e. focus requests to the WM which in turn decides if and how to handle them

12:28 <ifreund> leon-p: yeah, probably. But river itself will not know anything about e.g. tags

12:29 <leon-p> of course

16:56 <ifreund> river's got a page on my website now :)

16:56 <ifreund> https://isaacfreund.com/software/river/

16:58 <ifreund> next on my todo list is blog post + release, and maybe merge that scroll-factor PR

17:05 <LarstiQ> ifreund: looks nice! Should you link the `my longer term goals`, if those are written up somewhere?

17:05 <LarstiQ> ah, I hadn't gotten to the `Future Plans` part yet

17:07 <novakane> looking cool

17:19 <ifreund> thanks :)

18:26 <novakane> gonna need to update that IF. logo to go with the river one :P

19:58 <Guest3> hi, does someone has a tip for configuring my touchpad for river?

20:03 <novakane> Guest3: configuring which part of your touchpad? Anyway see riverctl(1) input configuration section to see all options

20:12 <Guest3> Thanks, I'll take a look. Scroll direction and I want that a tap to trigger a click

20:16 <novakane> Guest3: for tap to click it's `riverctl input <input-name> tap enabled`

20:18 <novakane> don't have scroll direction in mind though

20:19 <Guest3> thanks, how can I list my inputs?

20:29 <novakane> Guest3: `riverctl list-inputs`

20:36 <Guest3> ty