i3status-rust VS x11rb

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.

xdotool worked ... but I didn't want to depend on external command-line tools, so I decided to look for X11 bindings for Rust. The best library I could find was x11rb. It had very little documentation and almost no one used it (it was difficult to find people who could help me with it). Fortunately, it had a detailed tutorial. Still, it was a struggle to make things works sometimes.

I'm using x11rb, X11 Rust Bindings. I modified some code from this tutorial so that I'm listening to key presses from parent_win (screen.root) rather than win:

In the end, I decided to use x11rb: https://github.com/psychon/x11rb. This way I don't have to run external commands.

I'm trying to move a window (the GNOME terminal) with x11rb. I followed this tutorial. But the move_window function doesn't move the window.

I'm using x11rb to interact with a window created with gtk-rs. window_id is the ID of the window created with gtk-rs. window_id_2 is the ID of the window created with x11rb (for testing purposes).

I also checked x11rb, but I think it's too low level (and too complicated).

There is a comparison page in x11rb but it seems to be outdated w.r.t rust-xcb and the unsafe claims, so would appreciate other perspectives.

Do you have a source for that or any specifics on how it "can't handle" the usecases? There's already work in Rust around fully supporting X11 (for example https://github.com/bread-graphics/breadx or https://github.com/psychon/x11rb)

I was thinking about specializing x11rb which is a great library for interfacing with X11, to my specific single threaded use case.

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.