14:00 <random_river_use> hey, guys. How do I get app class in riverwm?

15:22 <Ratakor> Hello, is there a way to get a window dimension for grim?

15:32 <pkap> Ratakor: river does not expose window dimensions or x/y. However, there are new protocols for toplevel capture which are already in grim. It'll take some more time until this can be merged in river because it's waiting for a wlroots release.

15:33 <pkap> But it's already usable, even though is PR is in draft mode: https://codeberg.org/river/river/pulls/1290

15:35 <pkap> I am running this for some days now and it works very well.

15:40 <Ratakor> oh interesting thank you very much

16:08 <icky93> how do i get PID of a window?

16:33 <pkap> icky93: It's not a PID in the sense of process ID. It's a unique identifier that the compositor assigns to each toplevel. It's exposed via the ext-foreign-toplevel-list protocol. i think this is already included in the latest river release. Then you need a client like lswt to get the identifier.

16:33 <pkap> I use lswt -j to get it.

16:34 <pkap> Bu not sure if this is released in lswt or you need to build lswt from master.

16:43 <icky93> can i use those identifiers to get PID of focused window?

16:50 <pkap> No, toplevel identifiers are unrelated to PIDs.

16:50 <pkap> Why not use pgrep or ps or something like that?

16:52 <pkap> What do you want to achieve?

17:32 <icky93> like kill -9 to FOCUSED window or SIGSTOP/SIGCONT

18:05 <pkap> icky93: This is not possible with river. River does not expose PID for toplevels. Do other compositors do that?

18:21 <icky71> yes, in hyprland you can use hyprctl to retrieve lot of info + PID which responds for the window. In sway there is `swaymsg -t get_tree` which also prints PIDs. Wayfire also has this ability. Other compositors have this as well i guess, via plugins or smt

18:31 <pkap> Ah didn't know that this was even a thing.

18:33 <pkap> pkill or killall for the rare occasions when necessary is acceptable I think.