01:24 <questionable_ole> here's a question to whoever has the knowhow... waybar's wlr/taskbar module can send "activate" request using zwlr_foreign_toplevel_handle_v1_activate call. Now, if the app I'm trying to activate is on an inactive river tag the tag is not being switched to

01:25 <questionable_ole> is there a way to achieve the tag switching to the one that contains the app I'm trying to activate? And if so should that be river's code that does it, or some exception handling in waybar's module code?

02:09 <leon-p> questionable_ole: that's a known issue. the problem is not so much the implementation (which would be trivial), but rather that it's not simple to decide what river should actually do. Should it set those tags? Should it toggle them? Should it move the window to the active tags right now? Or should it do that and keep the windows old tags as well? All of these would be valid responses. We don't want to add yet another config option right now, so we left it ou

02:09 <leon-p> t for the time being.

02:12 <questionable_ole> leon-p: thanks. I was trying to understand where the change would take place, but it seems like it could be on river side according to you. I suppose it could also happen in waybar with a custom module that would essentially copy whatever code is happening in "river/tags" on tag click before sending the "activate" request. But, like you said that's doing one of the possible options you layed out

02:13 <questionable_ole> fwiw my view is - you have your clients layed out a certain way, switching active tag to the one which has the client you clicked from the taskbar is least invasive option

02:17 <questionable_ole> I just understood the flaw in my thinking - like you said a client might be assigned to more than one tag. In that case should they both be toggled or only first of them is also a valid question

02:17 <questionable_ole> what a mess

09:06 <getfliped69> I think I figured out what is happening, there is no wayland display in /run/user/1000/, that's why I get the blackscreen. I have no idea how to fix it.

14:21 <dagle> ifreund: I think I found out why my mousepointer stopped working. I think it was a fast spike in memory usage (a program allocating 20GB of ram) and then oomd killing the mouse pointer / trackpad.

19:50 <mattnite> Hey I bought a Magic Trackpad, can I set up any gestures in river?

20:29 <questionable_ole> mattnite: I'd guess you need to ensure you have a working driver for that for your distro, and see if the gestures are being captured as input events in an app like xev. If so then just map those in your init file to whatever you like

20:35 <mattnite> Okay sweet, I don’t know much about input on Linux and gestures on a Bluetooth device from apple are doubly dubious

20:36 <mattnite> But I tried this program called touchegg and it did react to a three finger swipe

20:36 <mattnite> The only problem was that it caused the program to crash on some assert

20:37 <mattnite> But thanks for the direction, I’ll update if I find anything