ifreund changed the topic of #river to: river - a dynamic tiling wayland compositor || https://github.com/ifreund/river || channel logs: https://libera.irclog.whitequark.org/river/
leon-p has quit [Quit: leaving]
<edrex[m]> has anyone created a general-purpose protocol explorer client, like eg d-feet for dbus? seems like that would be a fun exercise and maybe useful for other devs
<edrex[m]> just found #_oftc_#wayland:matrix.org
<wrl> ifreund: hey, should i create a GH issue for that xwayland crashing bug? it's been biting me pretty hard
novakane has joined #river
snakedye has quit [Ping timeout: 268 seconds]
snakedye has joined #river
notzmv has quit [Ping timeout: 256 seconds]
snakedye has quit [Ping timeout: 258 seconds]
dbuckley has quit [Ping timeout: 258 seconds]
dbuckley has joined #river
novakane has quit [Quit: WeeChat 3.2]
notzmv- has joined #river
notzmv- has quit [Ping timeout: 272 seconds]
novakane has joined #river
<ifreund> wrl: yes please, I haven't been able to reproduce or see where the bug is from that stack trace
snakedye has joined #river
novakane has quit [Quit: WeeChat 3.2]
<ifreund> wrl: if you want to help track it down, reproducind it while running river in valgrind could be *very* useful
<ifreund> prefereably with wlroots debug symbols as well, though that may not be 100% necessary
<ifreund> I spent a while looking through river's code trying to figure it out from the stack trace you gave me, but I couldn't figure out what river was doing wrong
<ifreund> sway seems to have nearly the exact same logic, so I suspect the stacktrace may be misleading and the real bug is some other memory issue, which valgrind is great at revealing
leon-p has joined #river
<leon-p> edrex[m]: if you want a protocol explorer, there is this: https://wayland.app/protocols/
<leon-p> although I personally don't find it particularly useful
<leon-p> after some time you just get used to reading the XML files
<ifreund> leon-p: I think edrex[m] was talking more about an actual wayland client used for introspection/debugging
<ifreund> edrex[m]: wlhax has been very useful for inspecting what complex clients like firefox are doing: https://git.sr.ht/~kennylevinsen/wlhax
notzmv has joined #river
notzmv has quit [Ping timeout: 276 seconds]
leon-p has quit [Quit: leaving]
anniehallmoon has joined #river
noopdecoder has joined #river
noopdecoder has quit [Quit: noopdecoder]
elshize has joined #river
noopdecoder has joined #river
leon-p has joined #river
noopdecoder has quit [Client Quit]
noopdecoder has joined #river
noopdecoder has quit [Client Quit]
novakane has joined #river
noopdecoder has joined #river
noopdecoder has quit [Client Quit]
elshize has quit [Ping timeout: 252 seconds]
elshize has joined #river
<leon-p> found another bug: views appearing while another one is fullscreened are not on the "recently focused"-list and will not be focused when all other views are closed
Nulo has joined #river
<Nulo> Hey! How do I set the keyboard layout?
<yyp> Nulo: set XKB_DEFAULT_LAYOUT environment variable
<Nulo> Is there a way to set options and variants?
<yyp> Yes, XKB_DEFAULT_OPTIONS
<Nulo> Okay, thanks! I assume there's no way to set it on runtime?
<yyp> There was some work on that
<leon-p> Nulo: not yet. I skipped keyboard when working on input configuration because it is not as straight forward to do
<yyp> I think you can set that in xkb context, no?
Nulo has quit [Quit: WeeChat 3.2]
Nulo has joined #river
<leon-p> yyp: yes, but it does not really map to our model of setting configs for individual devices
<leon-p> xkb layouts are a global thing, not per device
<leon-p> if you want per-device keyboard layouts, you have to "cheat" by changing the global layout depending on which device sends key events. sway does this IIRC
<leon-p> but I don't think it's worth the complexity TBH
<yyp> Well, xkb is not something that takes over the input system, you need to forward keys to it. So what prevents from just switching the context (1 configured device = 1 context) keys are sent to the selected device?
<yyp> *for the
<Nulo> Is there no way to hot-reload the config? Like, by resetting everything before re-running the config script
<yyp> No
<leon-p> Nulo: there is a plan to eventually have some sort of reset command.
<yyp> You can just re-run the config script, which does work 99% of the time unless you have something completely incorrect set up
<Nulo> Anything other than Waybar to use as a bar?
<yyp> yambar
<Nulo> Well, it keeps old keybindss that way
<yyp> It should override old keybindings
<leon-p> yyp: xkb does not actually send key chars to the clients. The server sends xkb key symbols to the client as well as some data to generate a keymap from. The keysym to char conversion happens client side. To change the layout, you have to send new layout data to the client.
<yyp> Ok
<leon-p> in practice this means per-device kb layouts are a little hacky, just as per-window layouts, but per-client layouts are perfectly supported
Nulo has quit [Ping timeout: 240 seconds]
elshize has quit [Ping timeout: 276 seconds]
elshize has joined #river
<snakedye> Nulo: I use eww for my bar
Nulo has joined #river
novakane has quit [Quit: WeeChat 3.2]
leon-p has quit [Quit: leaving]
<Nulo> Is there any resource for learning how to use river "in practice"? Maybe bspwm or dwm resources that also apply to river?
elshize has quit [Ping timeout: 272 seconds]
elshize has joined #river
elshize has quit [Ping timeout: 258 seconds]
elshize has joined #river
<Nulo> The media window from Telegram goes floating instead off fullscreen. This works fine in Sway
notzmv has joined #river
elshize has quit [Ping timeout: 272 seconds]
elshize has joined #river
elshize has quit [Client Quit]