i3status-rust VS Waybar

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.

If I understand https://github.com/Alexays/Waybar/wiki/Configuration correctly, what is to be displayed is defined in a JSON file that can be located in one of the directories mentioned.

GNU calls their extensions "equivalent to" things I'd have suggested trying ($_I or $-l), but I'm not sure if the equivalents are themselves GNU extensions, too. Regardless, reading this Waybar Github issue about %OI, I get the impression there was a regression at some point, in any case on March 27th 2022 someone says it "used to work fine until recently".

hope it helps. source btw: https://github.com/Alexays/Waybar/issues/2177

{ config, pkgs, ... }: { wayland.windowManager.sway = let patchedWaybar = pkgs.waybar.overrideAttrs(prev: final: { patches = [ (pkgs.fetchpatch { url = "https://github.com/Alexays/Waybar/pull/2134.diff"; sha256 = "1hzdv3b8zzps50pdcb8pj9cxwaix4q2d4gsqb9dl9vflgl429hq3"; }) ]; }); in { enable = true; config.bars = [{ statusCommand = "${patchedWaybar}/bin/waybar"; }]; };

See this issue. CSS and only new properties in config are reloaded when SIGUSR2 is triggered.

I think this has just been added to waybar (wlr/workspaces) to work in a similar manner to how it is in sway/workspaces. No need for fake empty terminals. Something was merged for wwlr/workspaces in the waybar github. See - https://github.com/Alexays/Waybar/pull/2089.

Ah, well in looking at their git, it appears some do have fallback font issues. See here - https://github.com/Alexays/Waybar/issues/215