05:55 <talismanick> Do all new touch features (e.g. MS pen protocol) need to be tested by running as the root instance?

10:21 <n0r> Do I need to be aware of anything special when starting multiple river instances on multiple ttys (for testing configurations) or should that "just work"? Rather ask before I end up having to force reboot because things got messy :D

10:23 <tiosgz> i guess just make sure that your init doesn't killall something you need

10:23 <tiosgz> and at times (though i don't remember if it was river or kiwmi) the "older" compositor crashed for me when i started the "newer"

10:24 <tiosgz> but if you don't need something drm-specific, nested river works well too

10:25 <n0r> I don't have any killall in the init. Important stuff is in tmux anyways. I just worried about idk some accidental loop I don't get out of or stuff like that.

10:46 <leon-p> n0r: should work fine, I do it often for testing changes. Just beware that a dbus session is different to a wayland session, meaning your new river instance might "steal" notifications and other dbus things

10:48 <n0r> I don't even have a notification system set up :D Seems to work right now, thanks.

12:57 <tiosgz> if anyone's interested, i've made up a layout generator https://codeberg.org/tiosgz/lespa

12:57 <tiosgz> but its '2n+1' system doesn't seem like a good idea in river with views constantly jumping around, so it may be a dead end

12:58 <tiosgz> anyway, feedback welcome

14:02 <NikhilSingh[m]1> tiosgz: mate I tried setting up multi-monitor and it is nice but how can I achive to seamlessly switch focus between my monito like if not any window is below the stack of current output it focuses on the next output.

14:02 <NikhilSingh[m]1> BTW left right focus will make it more feasible to do ( is it in plan to be there)

14:05 <leon-p> tiosgz: nice! a week more and I would have created the same, powered by $secret-project

14:07 <Ryan[m]12> ifreund: I saw that by the looks of your config you also use a secondary vertical monitor. What’s your workflow for your browser? That’s my biggest pain point I have since my main monitor is directly in front of me and my vertical monitor is off to the side so I don’t want to do super active browser tasks like PR reviews with my head turned to the side. I’m currently dragging Firefox tabs back and forth as needed. If you have a

14:07 <Ryan[m]12> similar use case, do you have anything more elegant for browser tab management across two windows?

14:12 <leon-p> Ryan[m]12: if one of your monitors is uncomfortable to look at, you may want to reconsider your desk setup. ergonomics are important

14:18 <Ryan[m]12> <leon-p> "Ryan: if one of your monitors is..." <- I might try something else for a bit, my thinking was It made sense to have my larger primary monitor squared up with me then the smaller vertical one off to the side more for documentation or entertainment or what have you. I wall mounted my monitors so moving them is fun 😁

14:21 <leon-p> maybe you can get the vertical monitor a bit farther away from the wall and tilt it more aggressively towards you, that should help

14:22 <leon-p> I also have two monitors and I also spend a few days getting their layout good enough, although I have simply abandoned the concept of "pimary screen" along the way

14:23 <Ryan[m]12> Are they the same size/orientation?

14:24 <leon-p> nope, one ultra-wide and one 4:3, so not even remotely the same :)

14:28 <NikhilSingh[m]1> From which package did xrandr got installed in my system?

14:30 <leon-p> NikhilSingh[m]1: that depends on what system you are running. However, all sane package managers will allow you to lookup which package a command is provided by (f.e. `pacman -F xrandr`)

14:30 <Ryan[m]12> NikhilSingh[m]1: Xrandr is used for configuring xorg displays, not wayland. You probably want some combination of wayland-utils for querying about your current monitor settings, wlr-randr for applying output configuration, wdisplays for a nice GUI, and kanshi for automatically configuring displays based on which are connected.

14:38 <NikhilSingh[m]1> leon-p: thanks mate

14:38 <NikhilSingh[m]1> I got to know that

14:38 <NikhilSingh[m]1> xrander needed by xorg-xsetxkbmap that is required by xorg-xwayland.

14:39 <NikhilSingh[m]1> Ryan: which command from Wayland-utils will help to figure out output name?

14:57 <Ryan[m]12> <NikhilSingh[m]1> "Ryan: which command from Wayland..." <- I think it’s “wayland-info,” don’t have my linux box handy to confirm.

14:58 <leon-p> wlr-randr is also a thing

14:59 <Ryan[m]12> Can wlr-randr query?

14:59 <ifreund> yeah just run it with no args

14:59 <Ryan[m]12> I thought it only applied randr config

14:59 <Ryan[m]12> Huh, my ability to not use computers gets better by the day

15:11 <crdpa> how can i change the keyboard layout to br?

15:11 <crdpa> portuguese brazilian

15:12 <leon-p> crdpa: you need to set an env var before starting river to set the keyboard layout, see river(1)

15:13 <crdpa> setting in .bash_profile isn't working

15:13 <crdpa> export XKB_DEFAULT_LAYOUT=br

15:14 <leon-p> if you changed .bash_profile, you need to re-log for the changes to apply

15:23 <crdpa> leon-p: It worked! thanks! Another question: how do i spawn something on the second tag on startup

15:26 <tiosgz> switch to second tag, spawn it. rules etc are not a thing in river (yet)

15:26 <crdpa> i see

15:26 <crdpa> thanks