10:50 <ifreund> leon-p: with the current output model that would make sense, but if/when we switch to a single shared tagset that becomes as simple as having output A focused then focusing the tag(s) currently displayed on output B

10:51 <ifreund> the only output specific command to remain would be focus-output, everything else would be done through tags

13:15 <leon-p> ah yeah, kinda forgot about that. makes sense.

13:17 <leon-p> since that will be breaking anyway, how about we take a look at the layout protocol again? I'd really like #383

18:04 <lxsameer> hey folks, I hope this question is not way off topic, but how do you develop and test river? do have something similar to Xephyr?

18:16 <kennylevinsen> wlroots compositors can run as Wayland or X11 clients

18:37 <lxsameer> kennylevinsen: ahhhh, nice

18:37 <lxsameer> thank you

20:20 <Guiltyfart> Hi, i have river running on void linux but none of the keybinds defined in the example init (which is in $XDG_CONFIG_HOME), mouse cursor is responsive so I'm assuming the issue is with the init script.

20:22 <leon-p> is your init executable?

20:23 <Guiltyfart> It is, currently chmod 777 permissions

20:25 <leon-p> with river launched, switch to another tty, export WAYLAND_DISPLAY=wayland-1 (higher number if you have other wayland compositors running) and try launching a terminal from there

20:27 <Guiltyfart> Getting font issues when i try to run foot, I'll fix this first

20:39 <Guiltyfart> I ran `riverctl exit` and the corresponding wayland display running river closed

20:40 <leon-p> so, which river version are you on and do you by any chance grabbed the example config from the github repo?

20:44 <Guiltyfart> it's river 1.1 and the example config is the one on the github repo

20:45 <Guiltyfart> after exiting river i noticed that there was some output `(EE) failed to read Wayland events: Broken pipe`

20:45 <leon-p> the current example config likely uses "Super" and "Alt" as modifier names, but they only got introduced with river 1.3 . You need to replace those with Mod4 and Mod1

20:46 <leon-p> that message is just a client complaining about the sudden disappearance of the server, nothing to worry about

20:48 <Guiltyfart> Changed the exit binding definition to use "Mod4" instead and it worked

20:48 <Guiltyfart> thanks very much for the assistance.

20:50 <leon-p> nice!