simple-osd-daemons VS i3blocks

I like the way crate2nix works. I have made a flake template for it here. Sometimes it requires a couple of overrides to fix some misbehaving crates (see https://github.com/balsoft/simple-osd-daemons/blob/master/flake.nix#L29 for an example of such overrides), but otherwise it's fantastic. It doesn't require any hash nonsense, it downloads and builds all the crates separately (unlike naersk or other solutions) so you get all the benefits of Nix (reproducibility and proper caching).

I have written a little tool that does something similar: it shows current volume, music track, battery percentage etc when they change (it's a bit like the OSD you see in DEs, but for your WM). Get the source here: https://github.com/balsoft/simple-osd-daemons

Another tool you can consider is i3blocks, which really is just a light layer on top of the default i3bar but uses a more readable config format.

But there is one issue background must wait for dunstify notifcation to finish (explained here in different context https://github.com/vivien/i3blocks/issues/354). This mean I can't take another screenshot until I dismiss/click this notification.

You can use the default swaybar with i3blocks as the status_command. i3blocks can receive signals.

From https://vivien.github.io/i3blocks/

You can think of yablocks as somewhere in between writing your own status generator manually using the i3bar json protocol and using i3blocks. You'll be generating the JSON output yourself, but with help from a fully featured templating engine and structured data.

within your i3blocks config. This solution doesn't always work, especially in firefox, and is prone to hanging. Even using :

I use i3blocks and write all the scripts myself, these examples can be a good starting point.

https://github.com/vivien/i3blocks.git https://github.com/vivien/i3blocks-contrib.git

https://github.com/vivien/i3blocks#click

You might check out https://github.com/vivien/i3blocks instead of i3status.