05:33 <LarstiQ> ifreund: I too want to echo the health maintainer over stressed maintainer viewpoint, the WM protocol looks exciting but in the mean time river as is is already quite good

07:34 <mekeor> hello :) chromium shows browser notifications in windows/views. how can i make these float? does anyone have `riverctl rule-add ... float` rules for it by hand? (i currently don't use any notification daemon. should i?)

07:39 <novakane> mekeor: you should yeah, even with a rule it probably juste gonna make a big centered window

07:40 <mekeor> novakane: do i need to add rules to river such that mako-views are not centered?

07:41 <novakane> no, if you use mako it should just works out of the box

07:43 <mekeor> novakane: cool. how does this work? doesn't mako just create windows/views just like any other application? or is it that river has default rules for mako?

07:43 <mekeor> i'm trying to understand what these notification daemons do :)

07:45 <ifreund> mako uses a different protocol than normal windows called wlr-layer-shell which is intended for desktop shell components

07:50 <mekeor> i see, makes sense to me now, thanks. since i neither like nor use notifications, i'll just disable them in my browser, and enjoy not needing another daemon.

08:01 <mekeor> another question. how to use `dbus-update-activation-environment --systemd WAYLAND_DISPLAY XDG_CURRENT_DESKTOP=river`? should it be put in river/init? should it be passed to `exec`? and placed at the end of river/init? or should i end the line with an ampersand `&`?

08:13 <ifreund> mekeor: anywhere in the init script should be fine

08:14 <ifreund> & is a shell feature to run a given command in the background without blocking

08:14 <ifreund> since that dbus command shouldn't block in the first place, & is not useful here

08:15 <mekeor> makes sense: it doesn't spawn a daemon, but rather it talks to the dbus daemon. thus, & is not needed.

08:15 <ifreund> exec is a shell feature that replaces the shell process with the given command, thats not what you want here

08:16 <mekeor> weird that i saw people use `exec` in this context!

13:55 <leon-p> mekeor: you might have seen people use exec at the end of their init script to replace the shell process with the layout generator

13:56 <leon-p> I think we dropped that from the example config because people were putting commands after that line and we had a lot of questions about those commands not running

13:57 <leon-p> I would have expected that anyone replacing their desktop with a pretty niche wayland server would know shell, but I have learned that people discover unix oddities in different orders

16:29 <choucavalier> leon-p: it's bottom up. the issue is more about people using a feature (exec) and lazily not investigating what that is before asking questions to other people

17:06 <crymeariver> Is there a way to get the currently active keyboard layout?

18:00 <nemoguest> mekeor this is probably because xdpw recommends it at the bottom of their wiki, both for river and sway: [https://github.com/emersion/xdg-desktop-portal-wlr/wiki/%22It-doesn't-work%22-Troubleshooting-Checklist]

18:01 <nemoguest> which is rather strange considering that sway 'exec' is different? And I think exec_always would be

18:01 <nemoguest>  preferrable in sway case...

19:07 <mekeor> thank y'all :)

23:42 <NickH> nemoguest: sway config is not a shell script, so to make it run a command you use the "exec" sway config command.