i3status-rust VS pgwm

If you want icons and clickable items on the bar you need to use something like https://github.com/greshake/i3status-rust

https://github.com/greshake/i3status-rust/tree/master/examples is about twice as good. The way i3blocks handles clicks is quite frankly kind of crap.

I assume you have installed latest stable version which is 0.22. The relavant config is https://github.com/greshake/i3status-rust/blob/v0.22.0/examples/config.toml

What's the version of i3-status you are using. As per their README, https://github.com/greshake/i3status-rust , there are two versions 0.22 and 0.3. Make sure you are using compatible versions according to your config.

Yeah, much better than the default i3status, it is well documented, you can check its screenshots and documents for more into. https://github.com/greshake/i3status-rust/blob/master/doc/themes.md

Setup is a Clevo laptop with an eGPU and 3 external monitors, running i3wm with i3status-rust. Keyboard is an Ergodone (chinese knockoff of ZSA's Ergodox EZ) with MX Browns and caps are a white and green set from AliExpress, that was basically the only DSA blank set for this keyboard I could find that would also have homing notches.

Ps. I don't at all endorse using tiny-std, I think it's correct but I wouldn't be surprised if some nasty bugs are hiding somewhere in there. Although I do use it for my WM pgwm which can now be build on stable, assuming you're running Linux with io-uring, a wrote a bit about that change here but didn't post about it then. The main benefit of tiny-std being tiny binaries that link statically.

If you want to check out the WM, that can be found here. If you want to check out tiny-std, that's here. As previously mentioned, there's a write-up on all of that here.

So if firefox is an application you can find you can query the WM_CLASS property, like this. Other applications might not set that and you'd have to use some other property or information to deduce that this given window(which is just a u32) is actually applicationA. A tip is to start the application, use xprop and see what properties it sets. call_wrapper.rs contains a lot of code about querying different properties. The x11rb example simple_window.rs has a few examples of the other side of that showing how an application can set its on properties.