01:21 <ifreund> novakane: Is

01:22 <ifreund> novakane: whoops, the one in the river repo has the 0BSD header now, feel free to grab that

01:23 <ifreund> haven't updated the gist yet, maybe I'll make it into a proper repo

02:16 <gbrlsnchs> will river 0.2 use Zig 0.10? I'm currently pinning Zig's version to 0.9 in Gentoo (luckily only river uses Zig in my system, so not a big deal)

03:12 <ifreund> gbrlsnchs: 0.2.0 will use 0.9 still and then I'll upgrade to 0.10 right away and release 0.2.1 compatible with zig 0.10

03:13 <gbrlsnchs> ifreund: cool, thanks! :-)

13:34 <leon-p> ifreund: I think you broke the resize command in 489a4973

13:34 <leon-p> resized views don't change their position anymore, the top-left corner remains stationary

13:35 <leon-p> which in turn broke the code that ensures views don't get resized out of bounds

13:57 <leon-p> opened a PR

17:43 <scorpion2185[m]> I can't start sway with nvidia. is possible that river would work?

17:45 <tleydxdy[m]> probably not

17:45 <scorpion2185[m]> can new driver version help?

17:46 <tleydxdy[m]> maybe

18:32 <scorpion2185[m]> debian wiki states "sway doesn't support nvidia proprietary driver in any form" so I guess it is the same for river

18:46 <scorpion2185[m]> noob question where is the command that make 9 tags in the example config?

18:50 <novakane> there is no command, there is always 32 tags that you can use

18:54 <scorpion2185[m]> but there aren't 9 tags active?

19:03 <leon-p> What do you mean with "active" here?

19:05 <scorpion2185[m]> waybar shows 9 tags when I use next/previous tag there are 9

19:10 <novakane> that usually something hardcoded or with an option client side not on river

19:12 <scorpion2185[m]> does some client support that?

19:12 <scorpion2185[m]> how can I change it in the code?

20:53 <jokeyrhyme[m]> I didn't think waybar actually supported river at all

20:54 <jokeyrhyme[m]> That's the workspace widget that it provides for sway, right?

20:54 <ifreund> jokeyrhyme[m]: waybar has several river specific modules

20:55 <jokeyrhyme[m]> Oh wow, it's been years since I looked at waybar

20:55 <jokeyrhyme[m]> Nice

20:55 <ifreund> scorpion2185[m]: waybar also has documentation for its river/tags module that should answer your question

21:04 <EmoSpice> Good afternoon - I'm trying to get river working in a nixos+home-manager setup. I'd like to use the home-manager services (kanshi, waybar etc). To do this, I need a systemd user target that is entered once river starts.

21:05 <scorpion2185[m]> I checked waybar doc you can hide the tags but they are there when I switch to next/previous tag

21:06 <scorpion2185[m]> hide them in the bar only

21:06 <EmoSpice> I have the systemd target built and installed and the two services in question are in ~/.config/system/user/river-session.target.wants, but on startup they both fail being unable to open the display. I am updating the dbus activation environment and the systemd environment with both DISPLAY and WAYLAND_DISPLAY. Does anyone have anyother ideas?

21:09 <EmoSpice> I'm happy to point at code for all of this, but I am afraid I don't really have a minimal repro case available.

21:11 <scorpion2185[m]> is there some client that let you change the tags? i didn't see any of that

21:12 <scorpion2185[m]> the number of tags

21:12 <EmoSpice> scorpion2185[m]: What are you trying to do? I missed the introduction of your problem

21:12 <scorpion2185[m]> EmoSpice: waybar shows 9 tags ,when I use next/previous tag ,there are 9. how can I change the number?

21:13 <EmoSpice> I think that `man waybar-river-tags` explains that

21:13 <scorpion2185[m]> >that usually something hardcoded or with an option client side not on river

21:15 <scorpion2185[m]> EmoSpice: I know that I can hide them on waybar , but they are just hidden only on the bar

21:15 <EmoSpice> scorpion2185[m]: Yes - river spawns a fixed number of 32 tags. They are always there.

21:16 <scorpion2185[m]> EmoSpice: with the example config there are 9 "active"

21:18 <EmoSpice> There's 3 layers to this: river spawns a fixed 32 tags. Your init file probably only binds keys for some subset of that. For instance, mine binds 1-4 to switch to tags 1,2,3,4, but the default binds 1-9 and 0 to show all tags.

21:20 <EmoSpice> The third layer is waybar. Waybar doesn't *know* about how many you have bound - only how many river spawned (a fixed 32, as I mentioned earlier). Waybar assumes you don't want to see all 32 and says "well, there's only 9 bound to keys by default, so just show the first 9"

21:20 <EmoSpice> scorpion2185[m]: ^

21:21 <EmoSpice> So you can bind keys to go to as many as you want, but "next" and "previous" don't *REALLY* make sense. Tags are a bitmask and can be composited together. What is "next" when your current view shows tags 1, 2, 5 and 7?

21:36 <EmoSpice> No one seems to have ideas, so I am going to hop off for a bit to test some theories of my own. I'll hop back in if I find anything productive.

23:18 <NickH> "next" in which context? Some riverctl command?

23:21 <NickH> For cycle-focused-tags, in that situation, next would be 2, 3, 6 and 8.