00:00 <novakane> Ah yeah true, well we just block the aur then :p

01:12 <ghostbuster> i went into the code and changed the check to accept >= 15 :-P

01:18 <ghostbuster> i'll just wait until 0.15.0 gets packaged for arch

01:22 <ghostbuster> i installed 0.15 from community-staging and now river fails because it's looking for libwlroots.so.11 but i have libwlroots.so.10 only

01:25 <ghostbuster> oh symlinking made it work.. i think it's working

01:34 <ghostbuster> this is cool.. excited to learn how to use it

03:00 <n8_> how have you added `swaybg` to your river init files? When I include it, my tiling breaks and river will float every window.

03:01 <n8_> my init script: https://git.nategb.xyz/stow.git/tree/river/.config/river/init

03:06 <n8_> hm. moving the contents of the line to riverctl spawn "..." worked.

04:27 <ghostbuster> so tags are unique per output? ie. the windows that I've tagged as tag 1 on monitor 1 are not related to which windows i've tagged with tag 1 on monitor 2?

05:10 <ghostbuster> oh i guess each window has a tag and an output, so if you move it to the other output the tag continues

06:55 <n8_> ghostbuster: I think that's correct, based on my experience

06:57 <ghostbuster> yeah i'm getting the hang of it

06:58 <ghostbuster> i can see it being quite powerful once you get your workflow dialed in

06:59 <ghostbuster> having a bit of flakiness with changing resolutions on my multi-monitor setup but i've had issues with sway as well so I am not convinced it's an issue with river

07:03 <n8_> ghostbuster: the other day on here, someone recommended me to use kanshi, which i think could also helo with the resolution problem

07:04 <ghostbuster> i've tried it before on sway

07:04 <n8_> no luck?

07:05 <ghostbuster> it's a cool project but it didn't resolve all the issues

07:05 <ghostbuster> i think part of my issue is that my laptop gpu can't drive 2x 4K displays _and_ the builtin laptop screen simultaneously

07:06 <ghostbuster> when i start river, even if the lid is closed, it seems to initialize eDP-1 and either DP-1 or DP-2 but what I need is for it to either initialize all three and mark eDP-1 as disabled, or not initialize it at all

07:06 <ghostbuster> what fixes it is manually disabling eDP-1 and then power cycling whichever monitor didn't get recognized

07:06 <n8_> i had a very similar issue. I used kanshi to set the laptop screen to not turn on if my monitor is plugged in

07:07 <n8_> viz. you can have it do what you described: only initialize DP-1 and DP-2

07:08 <ghostbuster> i will try it again, but judging from logs it already fails to initialize one of the two external displays before the river init is called, so I'm not sure when I would launch kanshi

07:08 <n8_> i have `kanshi &` as the first line of my river init

07:11 <n8_> https://git.nategb.xyz/stow.git/plain/river/.config/river/init

07:13 <ghostbuster> thanks

21:45 <ifreund> kraem: I my home row mods layout is starting to get comfy, here's what I've got currently: https://github.com/ifreund/qmk_firmware/tree/ff6594d34f6b3f55a33c50d0dbd61e33e2a10891/keyboards/crkbd/keymaps/ifreund

21:46 <ifreund> s/I //

21:48 <ifreund> messing up your muscle memory is a great way to get almost nothing done on a weekend, but I think it will be worth it long term.

21:49 <ifreund> having access to all mods on both hands solves some annoying usability issues I was having in certain situations with my previous layout

23:08 <kraem> ifreund: thanks. i'll try to find some time this week to try it out again