01:43 <tleydxdy[m]> oof the "lightweight" notification daemon mako is taking up 14g of my memory, also all of my swap too

01:44 <tleydxdy[m]> tho I didn't notice a thing, other than the browser slightly laggy

19:53 <mon_aaraj> hey everyone! I haven't been on IRC or river for a long while, as I switched to NixOS to try some things. But now I'm back on arch, and I wonder if now there's 1st class support for trying to get the current focused workspace?

20:30 <leon-p> mon_aaraj: you can get the focused tags via the river-control protocol, but that isn't new

20:31 <leon-p> s/river-control/river-info/

21:39 <mon_aaraj> oh, alright. thank you very much

22:07 <mon_aaraj> leon-p: About the river-info protocol, how would I use that in a shell script? Specifically for a statusbar to query if a workspace is urgent or occupied by a window, and which one is focused

22:09 <mon_aaraj> ah, wait, I'm getting deja vu, I'm guessing it is possible but there is no convenient way to do this?

22:40 <novakane> not with a shell script, you need a language with libwayland bindings

22:41 <novakane> so a client that would send the infos you want in some format and then you could parse it in your shell script

23:44 <leon-p> bash actually can open sockets, so /technically/ it's possible, but it wouldn't be very pleasant

23:46 <leon-p> mon_aaraj: you wouldn't want to do that in a shell script anyway. For propper UX you want something evented. Most status bars will implement the protocol directly.

23:48 <leon-p> FWIW writing wayland clients is pretty simple, so you don't need much prior experience to DIY it

23:57 <NickH> mon_aaraj: leon-p provided some template python code for this sort of thing.

23:58 <NickH> I used it to make a script to switch to the next/previous tags. Was pretty easy.

23:58 <NickH> See https://github.com/NickHastings/riverwm-utils