00:01 <ghostbuster> i didn't know github has a 'mark comment as off topic' feature

00:03 <ghostbuster> is the 'stack of views' that river manages a stack in the computer science meaning?

00:04 <leon-p> ghostbuster: it's a linear list. views can be inserted top or bottom (technically everwhere, but that is not exposed) and removed from everywhere.

00:04 <leon-p> and also swapped randomly

00:04 <leon-p> so no

00:05 <ghostbuster> so then when a tag is 'focused' on an output, the subset of the stack with that tag is rendered to an output, and the order of those views in the subset is used as a cue to the layout generator?

00:06 <leon-p> yep, that's about it

00:06 <leon-p> although to be a bit more precise, the view does not need to match the output tag, the two are &'d and if the result is non-zero, the view get's rendered

00:07 <ghostbuster> because you can focus more than one tag per output?

00:08 <leon-p> yep

00:08 <leon-p> and because views can also have more than one tag

00:09 <ghostbuster> right, that's a feature i haven't even played with

00:10 <ghostbuster> ifreund: you commented on that github issue that to have a single tagset across all outputs would require each view to have only one tag

00:10 <ghostbuster> i don't understand why that would be the case

00:11 <ghostbuster> is it to prevent a single view from being rendered on multiple outputs simultaneously?

00:13 <leon-p> yes, that's the reason

00:13 <leon-p> one view on multiple outputs and therefore in different layouts would be very awkward

00:13 <ghostbuster> ah yeah

00:15 <leon-p> also there are more general problems with a view on multiple outputs, as unfortunabley you'd have to use the same buffer for both. So which outputs DPI do you use for scaling? Which outputs colour configuration? WHich outputs refresh rate? etc...

00:16 <leon-p> that capability is really only intented for moving a view from one output over to the next one with the mouse, I think

00:22 <ghostbuster> yeah lots of weird edge cases to handle

00:23 <ghostbuster> i guess you could always let the user choose - you can have a single tagset, or you can have multiple tags per window, but not both :)

00:23 <leon-p> that kinda is the plan, actually, if evreything works out

00:24 <leon-p> the layout generator eventually will absorb that functionality, so that everyone can implement it the way they like

00:32 <ghostbuster> cool

00:59 <lgflorentino> I need some more help building river ... :(

00:59 <lgflorentino> using ArchLinux

01:00 <lgflorentino> wlroots in community is only 0.14 but the latest zig-wlroots requires 0.15

01:00 <lgflorentino> I've built wlroots separately and installed it to a dir. I can't seem to configure LD_LIBRARY_PATH properly to pick up the 0.15 wlroots so

01:01 <leon-p> lgflorentino: you can also just build an older version of river, might be easier

01:01 <leon-p> featurewise there hasn't been any major additions recently I think

01:01 <lgflorentino> older version of river i get errors about zig language features that are not available

01:01 <leon-p> I see

01:02 <lgflorentino> I can either wait for 0.15 to hit community which the archlinux channel didnt know when that would be

01:02 <leon-p> installing wlroots to /usr/local/lib and setting `export LD_LIBRARY_PATH=/usr/local/lib/:$LD_LIBRARY_PATH` in .profile works for me

01:02 <lgflorentino> or try and get river to build with the custom wlroots

01:03 <lgflorentino> Ok. Thank you. I shall try it

01:59 <lgflorentino> leon-p: thanks that worked with the /usr/local/lib path

01:59 <lgflorentino> I'm still not sure why it would not work with /opt/share/wlroots/lib

02:00 <lgflorentino> some magic in the background using only standard pathing maybe

02:03 <leon-p> maybe in the future we can setup the build system so that you can build and statically link a local copy of wlroots, so river no longer needs to depend on the version installed globally.

02:06 <lgflorentino> ifreund: thanks for the tips a couple of days ago. Xwayland is enabled now and the IDE runs with River. no more segfault :)

02:07 <lgflorentino> I had a look through the zig.build to see how to feed it the library but I'm not familiar with the build system so I wasn't able to figure it out

02:08 <lgflorentino> It makes a bit more sense if it was checking globals

02:21 <ghostbuster> you can just download wlroots 0.15 from staging https://archlinux.org/packages/community-staging/x86_64/wlroots/

02:30 <lgflorentino> :O That works as well. Thanks for the tip

03:07 <ghostbuster> np

03:07 <ghostbuster> now i am sure that wlr-randr is reporting the wrong mode for one of my external displays :-/

03:08 <ghostbuster> oh nvm, it's just not showing a bunch of modes

07:28 <Guest63> Hello all, I want to use the numbers on the keypad to switch between tags, how can I write that out in the init file?

07:29 <Guest63> the following line by line won't work ive tried

07:31 <Guest63>  # $mod KP_Up    set-focused-tags 7 #use keypad numbers

07:31 <Guest63>  # $mod KP_Prior set-focused-tags 8 #use keypad numbers

07:31 <Guest63> etc

09:16 <novakane> you need to use set-focused-tags 1, 2, 4, 8, 16, 32, 64 and so on

09:17 <novakane> ah, they left

09:17 <tiosgz`> but it's logged, innit?

09:18 <novakane> yep

09:19 <novakane> do people read the log though? I don't know :P

14:25 <leon-p> elshize: since we talked about it, I am currently using that online editor I mentioned with vim binds. If you want an accurate report of how annoying it is to temporarily switch back from kak to vim, ask me in an hour.

14:40 <elshize> leon-p: lol, ok

16:46 <angry_vincent> is WAYLAN_DISPLAY in example init void-linux specific?

16:46 <angry_vincent> so that where i added this variable on FreeBSD

16:58 <tiosgz`> leon-p: so how is it?

17:00 <tiosgz`> angry_vincent: WAYLAND_DISPLAY is the wayland equivalent of DISPLAY

17:01 <angry_vincent> okey, is this required for river?, i do not need to set it for sway, for example

17:02 <tiosgz`> you do not set it. it's set automatically by the compositor

17:02 <angry_vincent> thanks

17:03 <tiosgz`> if you set it, river would try to connect to the compositor at that socket (which is useful e.g. to run a nested session – but even for that you don't need to set it manually)

17:47 <leon-p> tiosgz`: ok, but the online editors implementation of the ~ key is apparently buggy, it matched neither vim nor kaka dn constantly tripped me up :P

17:47 <leon-p> *kak and

18:47 <elshize> leon-p: yeah, one thing about those online vim-mode editors is they're never a full implementation, there's always something that doesn't work