The rest is redundant.  On a healthy system, / does not need to be
watched so closely and libvirt/images uses sparse files so the info is
not so accurate.

I must admit, this is mostly because tab-friendliness, which pretty much
explains why I'm moving i3status but not i3 itself.

Has to match how it's defined in the order above.

 *  Avoid icons that don't work well on Debian (conflict in Private Use
    Unicode area).

 *  Simplify battery statuses even more (with better understanding
    of ACPI statuses).

At least once I ran into problems, not realizing that full / was the
cause.

Not funny.

Hey, those numbers are *rough* estimates...

Turns out low_threshold is in minutes, not in percent, by default.
Needless to say, time estimates are grossly unreliable here and 10
minutes left is too late anyway.

Most of numbers from 0 to 100 have 2 digits.