04:05 <Guest88> Hi! I’ve recently migrated from XMonad and I was wondering if there was a similar feature to NamedScratchPad

05:11 <RZ_MJ[m]> I don't exactly now how NamedScratchPad works. That being said, it is possible to use one or more tags as scratchpads. River has 32 tags. If you use 10 or 20 of them in a "normal" way, that leaves up to 22 or 12 of them which you could use as "scratchpad workspaces" if you keybind them cleverly.

07:44 <JustineSmithies> Sorry folks but I've another question which I can't find a definative answer for. On sway or qtile I could have mpv open floating and pinned to an output at a specific size so i could work away and always have the mpv window kind of like picture in picture in the bottom right corner of the screen i was working on. Will this ever be possible in River ?

07:47 <JustineSmithies> So basically I'd using rules match the class or app-id for mpv then float the window which you can do here and also size it to say 640 by 360 and move it to 1200 600

07:52 <RZ_MJ[m]> I have a keybinding to make a window appear on all tags. I think it even exists in the example init. Using that in combination with a float-filter rule and moving it where you want manually kind of does it. There is a problem though: keyboard focus will move to it for all changes of tag focus.

07:53 <RZ_MJ[m]> I found it in the example init: It is on line 98 (making use of line 96).

07:59 <RZ_MJ[m]> To list clearly what - to my knowledge - is (not) possible:

07:59 <RZ_MJ[m]> Floating: Possible by rule

07:59 <RZ_MJ[m]> Sticky: Possible by keybind, but buggy focus

08:00 <RZ_MJ[m]> Positioning: Possible manually, but not by rule

08:06 <JustineSmithies> RZ_MJ[m]: Thanks

08:36 <JustineSmithies> For my screenshot bind is it possible somehow to get the currently focussed output. I use 2 screens and I'd rather not have to screenshot both I'd like to be able to get the currently foccussed to pass to grim

08:36 <JustineSmithies> I know I can use grim and slurp to get a selected region as a workaround but it would be nice ;)

09:07 <tiosgz> humm... that focus thing makes me wonder if a command for pushing a view to the bottom of the focus stack would make sense

09:08 <tiosgz> JustineSmithies: (if you read the log) i think ristate can get you that info, though i've never used it myself

09:09 <tiosgz> ohh, lol.

09:09 <tiosgz> JustineSmithies: i think ristate can get you that info, though i've never used it myself

09:10 <tiosgz> (lol cos i sent that same thing just before you joined)

09:10 <JustineSmithies> tiosgz: Yeah I've just found that although not tried it yet either. Thanks

09:12 <JustineSmithies> Was just setting up my 3 screenshot mappings and logged out a few times to check everything in my config was still ok. Probs didn't have to do that but well....

10:31 <Guest92> Hello, i am unable to run river on fresh void linux install. Error 'Could not connect to socket /run/seatd.sock:  Permission denied'

10:33 <ifreund> Guest92: sounds like your user doesn't have permession to access /run/seatd.sock

10:33 <ifreund> you should fix that...

10:52 <Guest92> ifreund: how can i give a user permission to it?

10:53 <ifreund> https://docs.voidlinux.org/config/session-management.html#seatd

11:06 <Guest92> ifreund: Thanks. But another issue has occured - 'Could not initialize rendererdev/dri/card0 (vmwgfx)'

11:55 <ifreund> sounds like an issue with your graphics drivers

16:36 <leon-p> I wonder how realistic it is to get releases of wayland-protocols and wlroots soon-ish

16:36 <leon-p> I really want ext-foreign-toplevel-info

16:38 <leon-p> alternatively we could use the current wlr-foreign-toplevel-management for now. the uniqie view ID thing I plan to build on top could then be ported to the new protocol trivially

16:40 <leon-p> either way, I am convinced this would solve at least half of the common requests for scriptability we get

19:36 <JustineSmithies> Here's a weird one. I'm not sure what I've done different between two machines but neofetch on my test laptop on void running river shows WM: river yet on my daily it doesn't show WM

19:36 <JustineSmithies> If I set XDG_CURRENT_DESKTOP=river then obviously it then displays DE: river (wayland)

19:36 <JustineSmithies> Any ideas as they are both started the same with dbus-run-session river

20:22 <leon-p> is the config different between the two devices? I have in my config `systemctl --user import-environment WAYLAND_DISPLAY XDG_CURRENT_DESKTOP PATH

20:22 <leon-p> `

20:23 <leon-p> and systemctl --user import-environment WAYLAND_DISPLAY XDG_CURRENT_DESKTOP PATH

20:23 <leon-p> `

20:23 <leon-p> which do manipulate env

20:23 <leon-p> oh, I mangled the copy-paste, nice

20:23 <leon-p> I meant this one: dbus-update-activation-environment --systemd WAYLAND_DISPLAY XDG_CURRENT_DESKTOP=river

20:28 <JustineSmithies> I'm on void so no systemd ;) Both laptops are on void and there must be something different but I'm struggling to see what ?

20:29 <JustineSmithies> Both versions of neofetch and their configs are the same also checked for fuser on both as that is a dep of neofetch too

20:38 <leon-p> I guess you could strace it to see where the "river" string comes from

20:40 <leon-p> ah wait, I think I remember

20:40 <leon-p> IIRC neofetch uses pgrep to find the name of the wayland compositor. It has a list of compositors is goes through, one by one, and just returns the first one pgrep returns a PID for

20:41 <leon-p> so if you also have sway running on another TTY and if it checks for sway first (which I think it does) then it will display sway and not river

20:57 <JustineSmithies> Doh ! Found it.... my test laptop has a version that correctly detects river whereas my daily has the latest git version and it's code is slightly different and doesn't detect the WM yet it will display DE: river (Wayland) if I set XDG_CURRENT_DESKTOP=river . But that's wrong as River is a WM.

20:59 <leon-p> If "DE" meant "desktop" instead of "desktop environment" it would be close, because river does a lot more than just manage windows

21:00 <JustineSmithies> I know what's wrong now because fuser is being detected it's using that to try and determine the WM and failing. If i comment that line out it bypasses that check and correctly guesses the wm and displays it.