i3status.git/include, branch 2.12

Add IPv6 address when IPv4 isn't available (#247)

2017-12-11T10:38:31+00:00

Multiple CPU support for cpu_usage (#209)

2017-03-26T10:54:07+00:00

This change addresses the issue #199 asking for multiple CPU support. It takes an arbitrary CPU number and outputs its usage using the same arithmetics as for CPU aggregation. It currently doesn't support FreeBSD.

Fix i3status to compile with -fno-common (#185)

2016-12-13T18:32:57+00:00

This avoids multiple declarations of the same global variable in different source files.

Add 'format_below_threshold' option for 'disk' module

2016-11-14T23:09:05+00:00

Add 'format_above_threshold' option for 'cpu_temperature' module Add 'format_above_threshold' option for 'cpu_usage' module Add 'format_above_threshold' option for 'load' module

Setting of custom locale in tztime configuration. (#168)

2016-10-24T06:43:04+00:00

To be able to show my birth country's time zone in that country's locale, and my local time in my current locale.

Detect batteries using glob (#163)

2016-10-23T19:20:31+00:00

pulse device may be specified by name (#126) (#162)

2016-09-14T07:26:45+00:00

Implement aggregates for batteries.

2016-08-28T13:29:08+00:00

Using title number all, this enables aggregates. Note that FreeBSD and OpenBSD previously only reported aggregates, so this is bringing Linux and NetBSD that functionality. Changes the default battery reporting to the aggregate since most users probably don't care about individual batteries. For single-battery systems there should be no change. Fixes one obvious memory leak in NetBSD.

Parse uevent file to detect network device type (#153)

2016-08-22T17:23:59+00:00

Currently i3status differentiates wireless and wired devices based on the existence of wireless directory inside the device's sysfs directory. This approach seems to cause 3g modems to be incorrectly identified as the first ethernet device. This commit solves this problem by using DEVTYPE variable from uevent file. Signed-off-by: Cihangir Akturk

Add CPU usage color thresholds

2016-04-13T16:11:32+00:00

CPU usage had previously not supported the color option. Add support for a "degraded" state above which the degraded color is used, and a higher "bad" state above which the "bad" color is used. One possible use for these might be indicating whether one or all cores are saturated. Unlike the color settings for other, these are set high enough to be disabled by default. This is done because i3status determines CPU usage over only the last display interval, which means that, a user with a low refresh rate might see frequent, potentially-annoying color changes.