Hi! First, thanks so much @codic12 for creating worm wm and putting together a CE spin for it! It works well out of the box and I’ve been having a great time with it.
With that said, I’ve been fiddling with bars for the last week or so, and I’m wondering which EWMH atoms are supported in Worm WM? Polybar’s xwindow module doesn’t seem to want to recognize the focused window (which would require support for the _NET_ACTIVE_WINDOW atom.) Haven’t found any answers in the worm docs and, after looking over the EWMH spec, am not certain how to find out. Wondered whether anyone here might know.
Distro is EndeavourOS CE worm edition, compositor is picom, hardware is a Lenovo IdeaPad 5 15IIL05, and I have concurrent polybar and tint2 windows both running if any of the above matters.
Welcome to the EndeavourOS forum. I hope you enjoy your time here.
In line one of your post, if you put a @ in front of codic12, the next time he logs in, he will receive a notification saying he was mentioned in a post. I don’t know if that was your intention or not. Just letting you know as this may result in a faster response.
Sorry, I am sure you know more about worm than me, so I can’t be of help there.
Hi! Thanks for the clarification - I wasn’t certain whether @ mentions were implemented here (and I know some people and forums consider them rude, so wasn’t sure what the norm would be.) Thanks for the kind greeting as well!
hello! no @ mentions aren’t considered rude here at all and sory for the delayed reply! if you still need it, well there’s a large enum here https://github.com/codic12/worm/blob/main/src/atoms.nim but not all of them are actually supported
_NET_ACTIVE_WINDOW is currently not supported, unfortuntaely, but I can try to add it now however you can do it yourself by getting the top/raised window with xdotool if polybar lets you do that
Thanks for the response, and no worries on the timeframe, I don’t expect devs to be at my beck and call . As far as I’m aware, polybar won’t accept the results of xdotools’ getactivewindow as an input (although I may mess with it just to check.) But in any case it’s not a huge issue as tint2 works fine for now! If and when you do find time to implement it, I’m sure I’ll see it in the version notes and try again at that time but there’s no rush. Thanks for letting me know!