04:29 <talismanick> Is there a Wayland-native clipboard management system which lets you browse what you've cut & copied?

04:30 <talismanick> (like Emacs's "kill ring" - I think Vim has packages for something similar)

04:30 <talismanick> ...registers? idk

06:42 <talismanick> Also, how do I register which screen/output is "active"? (had the most recent keyboard or mouse event)

07:05 <talismanick> Maybe use libinput to find the mouse and register its location?

08:06 <talismanick> How do I list output devices (screens) on Wayland? xrandr doesn't work, and wlr-randr just says WL-1 (a kind of logical display?)

08:08 <talismanick> nvm, kanshi appears to accept WL-1. But, attaching a second monitor via HDMI cable only stretched the output double horizontally, with wlr-randr still reporting WL-1 as the sole display

08:12 <ifreund> talismanick: are you running river nested inside another wayland compositor?

08:13 <ifreund> the WL-1 output name seems to indicate you are

08:13 <AryaKiran> there is clipman

08:14 <talismanick> ifreund: I don't think so?

08:14 <ifreund> talismanick: how are you starting river?

08:15 <talismanick> similar script to your dotfiles

08:15 <ifreund> so running straight from a tty?

08:15 <talismanick> yeah

08:15 <talismanick> https://0x0.st/oMaN.sh

08:16 <talismanick> Oh, it might the `cage -s` call

08:16 <ifreund> yeah, you're starting river inside cage

08:16 <talismanick> Not able to switch ttys with it regardless, so I think I'll get rid of it

08:17 <ifreund> why even do that in the first place?

08:19 <talismanick> ifreund: I think I read something about that being part of enabling switching ttys like in Xorg (Ctrl+Alt+f2-11)

08:19 <ifreund> river allows that if you run it directly from a tty

08:20 <talismanick> Hm. Let me reboot and try again.

08:41 <talismanick> ifreund: You were right! Not sure why I couldn't switch ttys the first time I launched river (from a tty, no less)

08:43 <talismanick> on a related note, though, it appears to cause kanshi trouble if you switch ttys

08:44 <ifreund> what trouble, it works fine for me

08:45 <talismanick> my second screen gets stuck on the tty after I switch back to the graphical session

08:47 <ifreund> that doesn't sound like an issue with kanshi, perhaps a wlroots issue instead

08:47 <talismanick> okay, works if I turn the display off and on again

08:47 <ifreund> maybe try switching back to a tty, waiting a few seconds, then trying again?

08:49 <talismanick> nope

21:59 <pmnw> What is everyone's worflow with river? Do you use scripts around riverctl to manage tags actively? Asking because on sway there's auto assingnment of workspaces for chosen programs, so a lot of the work can be programmed into the config - as in: always open the browser on workspace 2. I'm wondering what kind of automation can be done with river atm.

22:10 <leon-p> pmnw: not much, since you can't adress individual windows right now, only the focused one. Although I find that for myself the only automation I need is the layout. Doing everything else myself as it comes up is a lot more flexible; going back to assigning workspaces/tags to certain programs just seems a bit silly now to me at least.

22:20 <pmnw> leon-p: I see the point in keeping things simple, not least in preventing river from morphing into a sway clone. Since a lot of the management is a shortcut away, it's not a big issue. Still, having programs likely to persist throughout a session like a password manager or the browser open in a delegated space, be it tag or workspace or scratchpad, is something I value highly. I'm sure a comfortable setup that minimises active

22:20 <pmnw> management can be done in river, I just haven't cracked it quite yet.

22:25 <leon-p> currently it is unfortunately not possible to assign a window to a tag(-set), so don't try to hard to "crack" it

22:34 <pmnw> Right, I know - I'm actually sniffing around river precisely to see how a decent workflow could be achieved outside of my sway paradigm.

22:43 <leon-p> pmnw: if you do want to get into automation, check out what protocols river implements and which of their events / request are supported. Not every capability is exposed through riverctl :)

22:57 <ghostbuster> tbh i usually run one window per workspace and leave it at that