00:27 <chooky> am I correct in understand that because the river config gets executed multiple times "The default river init is a shell script executing riverctl a bunch of times to configure river", putting something like `riverctl spawn x` would not be a good idea, i.e. `riverctl spawn waybar`

00:39 <chooky> Is there a way for me to set only the inbuilt keyboard to have a certain layout. looking at the man pages it seems any keyboard settings affects all keyboards.

11:46 <chooky> Hey guys, would anyone know why running [wlhangul](https://github.com/emersion/wlhangul) seems to freeze river completely... I've tried running river with debug logs but nothing seems to be output at all before or during the freeze.... It wont unfreeze until I restart the computer. any help would be appreciated!

11:51 <ifreund> chooky: what river version are you using?

11:52 <chooky> ifreund, sorry. I should've mentioned that. I'm running Linux 6.10.12-200.fc40.x86_64 Fedora 40 with river version 0.3.5 installed via dnf

11:52 <ifreund> seogi seems to work fine for me fwiw and appears to be an update wlhangul fork: https://github.com/mswiger/seogi

11:53 <ifreund> what you describe could be a river bug, hard to say without logs though

11:53 <chooky> oh, tbh I didn't even know this existed. I'll give it a shot now! thanks for that

11:54 <chooky> ifreund, I tried redirecting the output of river with `-log-level debug` but that didn't seem to produce anything. I'm not in the know how on how to debug on Linux past that point.. Sorry. I'll give seogi a go but if you have any recommendations on how else I could debug this issue I'll go ahead and try get some logs and log an issue on the river

11:54 <chooky> repo

11:55 <ifreund> chooky: river logs to stderr, did you redirect stdout or stderr?

11:55 <ifreund> river -log-level debug 2> /tmp/river.log should work

11:55 <chooky> ahhh sh,, nice catch. I was just `>`

11:56 <chooky> let me try seogi while my computer is running. then I'll try logging with `2>` as I will need to restart my computer after it freezes

11:56 <ifreund> also, to recover without a reboot you can probably use sysrq+r to reclaim the keyboard from river and then switch ttys

11:57 <chooky> interesting. usually I can get to ttys without needing to hit `sysrq+r` but river completely blocked that. Let me give it a go

11:57 <chooky> sorry if this sounds dumb... where is `sysrq` on the keyboard...

11:57 <ifreund> tty switching is implemented by the compositor, so it won't work if the compositor is not responding

11:57 <chooky> ahhhh, that's good to know. thanks for that

11:58 <ifreund> this could help you out, how exactly to activate sysrq depends on your hardware: https://en.wikipedia.org/wiki/Magic_SysRq_key

11:58 <vyivel> i'm assuming something like this https://github.com/swaywm/sway/blob/17e2e52c6d1bf4bfebde8f6b2869702aacc3750a/sway/input/keyboard.c#L387

11:58 <chooky> cheers. I'll finish building seogi then i'll give it a shot and try get some logs. I really appreciate the help

11:59 <vyivel> or hm

11:59 <ifreund> no problem!

12:00 <vyivel> from the server logs river gets zwp_virtual_keyboard_v1.keymap, responds with two wl_keyboard.keymap events and one zwp_input_method_keyboard_grab_v2.keymap event, and then it repeats

12:00 <vyivel> (0.3.5)

12:01 <ifreund> hmm, I can't reproduce a river hang on river's master branch which shouldn't be any different than 0.3.5 here

12:01 <ifreund> wlhangul works for a little bit and then crashes

12:01 <ifreund> segoi and fcitx work perfectly as far as I can tell

12:02 <chooky> ifreund seogi seems to be working perfectly so maybe i'll just switch to that

12:02 <chooky> i didn't realise it existed but glad to know about it

12:02 <vyivel> https://0x0.st/X6la.png

12:03 <chooky> when I attempt to run `wlhangul` it chugs the computer for a couple seconds then completley hangs on my machine..

12:03 <chooky> *completely

12:03 <ifreund> classic vyivel, debugging everyone else's compositors for them :D

12:03 <chooky> hahaha, I really appreciate it vyivel!!

12:03 <ifreund> crossiant's SSD is looking nice by the way :)

12:04 <vyivel> no shadows yet tho

12:04 <vyivel> anthywl works fine fwiw

12:05 <chooky> I think this and the limited keyboard input customisation have been my only two issues with river so far. apart from them, it's been wonderful to use. drove it today at work and everything worked fine

12:09 <chooky> ifreund how were you turning on seogi? it seems `wtype -k Hangul` isn't causing it to toggle on and off :thinking:

12:10 <ifreund> chooky: did you run `seogi -k Hangul`?

12:10 <chooky> yeah, I tried that (the help menu does say that's default as well)

12:11 <ifreund> hmm, I don't have a Hangul key on my keyboard but testing with something silly like `seogi -k g` works

12:11 <chooky> hmmm, you're right... that does work. I wonder why it doesn't pick up on `wtype`'s `Hangul` key...

12:11 <chooky> I don't have a hangul key either lol, hence the usage of `wtype`

12:13 <chooky> hmm, seems it's not picking up any keys `wtype` sends as sending `g` doesn't get picked up either

12:16 <ifreund> yeah, wtype doesn't seem to work with either seogi or fcitx

12:16 <ifreund> not sure why off the top of my head, haven't looked at this stuff in a while

12:17 <chooky> that's all good. I guess i'll look for an alternative. thanks for checking that!

12:17 <chooky> I really appreciate the help ifreund and vyivel! <3

12:17 <chooky> you guys wouldn't happen to know about this one by chance?

12:17 <chooky> > Is there a way for me to set only the inbuilt keyboard to have a certain layout. looking at the man pages it seems any keyboard settings affects all keyboards.

12:18 <ifreund> yeah, river doesn't support setting different layouts for different physical keyboards yet

12:18 <chooky> e.g. I wan't my inbuilt keyboard to run colemak but my external keyboard to be registered as qwerty as colemak is configured within the external board itself

12:19 <ifreund> tracking issue: https://codeberg.org/river/river/issues/400

12:19 <chooky> all good :) I'll setup a bind to just switch my inbuilt keyboard from colemak to intl. thanks for confirming that

13:23 <sewn> vyivel: ok good it shouldnt be a dynamic length

13:23 <sewn> why would someone send status text longer than the bar can display

13:25 <sewn> leon-p: hey!! where issue

15:00 <__toor__> ANSI keyboards is the way God intended. I use us-intl to typ in those pesky äåö when I need em.