04:33 <crypt_> hi I have a bit of code that ti am trying to get working to add a new bit of positioning code for adding a new view.

04:35 <crypt_> I have the following but it does not compile and ti am not sure why

04:35 <crypt_> const first = self.first;

04:35 <crypt_> const second = self.first.next;

04:35 <crypt_> if (second != null) {

04:35 <crypt_> any ideas?

04:37 <crypt_> this is within ViewStack

07:18 <user181308142001> Hi, does anyone know of a simple program to output the currently focused tags in river? I know this is possible with river-status-unstable-v1.h, but I cannot find a simple program that uses this protocal to print to stdout. I am willinging to do some pharsing on the data, so if there is a program that outpus all tags with more info etc., please let

07:18 <user181308142001> me know also. Thanks a lot :)

07:29 <bfiedler> user181308142001: there is ristate

07:51 <ifreund> crypt_: could you put the error you're getting in a pastebin?

08:08 <guest23> hola, how to move windows from one screen to another? To current active tag on another screen? Right now it moves to the same tag, not visible one

08:12 <bfiedler> I think you can use distinct tags on both screens

08:23 <user181308142001> bfiedler: thanks a lot, I was using yambar's debug logs as a placeholder, this seems much better though :)

08:59 <crypt_> https://pastebin.com/YXj4Qj9L

09:00 <crypt_> zig build

09:00 <crypt_> ./river/view_stack.zig:89:33: error: type '?*view_stack.Node' does not support field access

09:00 <ifreund> crypt_: first is an optional pointer, so you need to either check if it's null or assert that it's not null before accessing the data

09:00 <crypt_> const second = first.next;

09:00 <crypt_> ^

09:00 <crypt_> river...The following command exited with error code 1:

09:01 <crypt_> ah i think that I have much more to learn about zig

09:01 <ifreund> zig just stopped you from writing code that would segfault if there were no views in the view stack

09:02 <crypt_> that is a good thing - just a bit confusing at the start

09:02 <novakane> you should look at https://ziglang.org/documentation/0.8.1/#Optionals and https://ziglang.org/documentation/0.8.1/#while-with-Optionals

09:03 <ifreund> yeah the error messages definitely aren't all that great yet, the language isn't 1.0

09:04 <crypt_> well at least zig does not seem to have the new feature of the week tht rust appears to have

09:04 <ifreund> oh yes, zig is *way* simpler than rust

09:05 <ifreund> if you're already familiar with C or something similar you should be able to get up to speed on zig in a matter of days

09:05 <crypt_> the biggest issue that I have with zig is getting my head around using allocators

09:06 <crypt_> I have been using memory managed languages like python and lua for too long

09:13 <crypt_> well there re times that I missed one of the features of my old x200 thinkpad. It always told you in no uncertain terms when it was about to go flat

09:18 <guest23> another question - why Save as dialog not opening in Chrome? Any ideas?

09:31 <guest23> and there was a fork of river with double borders which is not available at the moment, do you aware why so?

09:45 <guest23> bfiedler can you please elaborate on using distinct tags on different views? trying to fit my head around tags/views

09:49 <novakane> guest23: I recommend you read this https://github.com/ifreund/river/wiki/How-tags-work

09:49 <guest23> thanks

09:51 <guest23> make more sense now

09:53 <novakane> view is just an other word for window and tags are really powerful but it take some time to be used to it

09:54 <guest23> started yesterday, after sway it is already better

09:54 <guest23> prefer dynamic tiling

09:55 <guest23> and happy about wayland in general, switched to it couple weeks ago because of different dpi screens

09:56 <guest23> played with scale and transform in X a lot, but performance never been like with river

09:56 <novakane> yeah this is probably the main reason why we all using river instead of sway here, I can't stand manual tilling

10:22 <guest23> any suggestion for a bar with ready to use config for river? Which can be hidden by hotkey

11:07 <pkap> Waybar can be toggled with the SIGUSR1 signal.

11:08 <pkap> eg. `pkill -SIGUSR1 -x waybar`

11:13 <guest23> thanks pkap, probably don't need a bar, strted to test river-popup-overlay

11:13 <ifreund> I use https://git.sr.ht/~leon_plickat/river-tag-overlay on my laptop as the screen is quite small for a bar

11:13 <guest23> ifreund perfect

11:14 <guest23> this is what i mean, river-tag-overlay

11:14 <guest23> need to add a binding for time/battery notification

11:14 <guest23> do you using any kind of notification for brightness/volume?

11:18 <ifreund> nope, I haven't been using my laptop hardly at all since covid started so I haven't found time to

11:18 <ifreund> simply using notify-send with mako should work pretty well though

11:19 <ifreund> this might be useful for battery notifications: https://sr.ht/~kennylevinsen/poweralertd/

11:19 <ifreund> alternative to mako: https://codeberg.org/dnkl/fnott

11:19 <guest23> thank you!

14:15 <guest23> anybody using musl void on daily basis? Curious to understand what kind of issues possible there

14:15 <ifreund> you're probably better off asking in #voidlinux

14:18 <guest23> curious to know according to the usage of Wayland and river

14:18 <guest23> but yeah, you are right, thanks

14:40 <ifreund> guest23: I run void musl on my laptop, river works fine

22:10 <crypt_> ifreund: thanks very much my after_top attach_mode code now works

22:34 <crypt_> ok i am now confused. It works fine but only on tag 1

22:45 <leon-p> crypt_: I missed that discussion, but I assume you are trying to create a new setting for attach_mode to attach views after the top view, right?

22:45 <leon-p> In that case, remember that there only is a single stack across all tags of an output

22:46 <leon-p> and the first visible view is not necessarily the top view

23:29 <crypt_> yes I basically just did a wrapper round the attach-top that then does a swap afterwards

23:30 <crypt_> ah that makes sense now

23:31 <crypt_> so I need to do a filter to wind the first it

23:31 <crypt_> tem for the tag that I am looking at

23:31 <crypt_> I see that there are filter functions there

23:44 <crypt_> would I be right in saying that ti should be using the iter method for what I am wanting to do?