Max Verevkin

The current theming model assigns each "state" a foreground and background. It is not clear how to apply a background to a single value. I mean we can, but it...

> Presumably the clickable icons would still have to be separate. Correct. Clickable elements are the reason why blocks are split. Since full-format and short-format may have different sets of...

Custom shortening priority sounds good for customizability, but I'm not sure how practical it would be. Another option would be to extend the protocol with "group id", not sure if...

From the mentioned i3's issue: > This maybe could also be combined with a preference factor (of keeping full size) which can be given by the JSON api. > I...

I had no plans to write it myself, because I'm not familiar with it. Would happily accept a PR though. By the way, all your examples use `.in` template files...

Since async-io v2 already requires AsFd, I went ahead and switched to OwnedFd from RawFd.

> such that the maximum number of blocks retain their full length > treat all blocks as having the same priority and thus shrink the blocks in order Shrinking blocks...

> I think length-based prioritization can be chaotic as different blocks can change their length dynamically As a user of a bar with "delta-length" prioritization implemented, I can say that...

FYI I've included this fix in https://github.com/MaxVerevkin/neli-wifi

> This doesn't seem to be possible in i3bar-river as far as I can see? Correct. I wasn't aware of this feature of i3/sway.