08:57 <ifreund> NickH: thanks for testing!

08:58 <ifreund> xaltsc: it only does exact string matches currently, we had the intention of extending it to support simple globbing but I've had other priorities as I don't personally have a use-case

08:59 <ifreund> ghostbuster: riverctl should not report an error on applying configs to a non-existent input

08:59 <ifreund> that must be supported so that one can e.g. configure a USB mouse that you only sometimes have plugged in on startup

16:41 <novakane> oh, busy day in river, lot of mails in my inbox :P

16:41 <pmnw> Hey - to those of you who don't use a status bar - what's your solution for checking some occasionally-useful information such as the current time (inb4 analog clock on the wall) or the keyboard layout, or current volume - in short: all the things that people usually put in their status bars?

16:42 <novakane> I used to have a keybind to send a notif with all infos I want

16:43 <novakane> just the clock, battery and volume

16:43 <pmnw> novakane: >used to --- what happened then?

16:46 <novakane> pmnw: I made a statusbar so I used this currently

16:48 <ifreund> status bars should really give an option to show/hide themselves on demand

16:48 <ifreund> maybe some do, I haven't really looked

16:49 <nor[m]> I just look those up in terminal - because I never bothered setting up a notification system either (I tell myself having notifications and ending up making lots of such Info-notifications will get as distracting as a bar) and I rarely need them anyway :D

16:50 <nor[m]> ifreund: I did that in Sway for a while with Swaybar.

16:50 <pmnw> ifreund: I think the compositors could do that, i.e. show & hide the status bar with a keybinding?

16:51 <pmnw> nor[m]: That's a good point. Once you use a notification system, you begin looking to put those notify-sends in all your scripts, which can be nice, but it's a headache.

16:51 <ifreund> pmnw: it would be technically possible yes, but river isn't really aware that the long skinny layer-shell client is a status bar

16:52 <ifreund> and I think it's generally better to do stuff like this which can be easily implemented client-side in the clients

16:53 <pmnw> ifreund: philosophically, I agree.

16:54 <nor[m]> pmnw: Not saying having them is a bad thing. Thats maybe just my excuse for being lazy xD

16:54 <pmnw> nor[m]: just giving you more reasons to stay that way ;)

16:57 <novakane> ifreund: would the status bar needs to be destroyed and initialized again or you could make somthing to just hide th surface or something like that

16:58 <novakane> toggling it is something I'd like to add to my status bar, just not to motivated to touch the wayland part these days

16:59 <ifreund> novakane: you can just unmap the surface

16:59 <pmnw> Hiding - because killing or restarting should be easily doable through scripts - which btw is nice if you don't want the thing to keep polling.

16:59 <ifreund> (commit a null buffer)

17:00 <novakane> oh yeah, I need to try

17:08 <novakane> the most annoying thing would probably be to send the toggle command to the bar without starting a new bar, that would be the first thing I need to think about when I want to make this