[no description] http://git.sigexec.com/cgit.cgi/i3status.git/atom?h=2.12 2018-04-08T13:53:19+00:00 2018-04-08T13:53:19+00:00 Ingo Bürk admin@airblader.de 2018-04-08T13:53:19+00:00 urn:sha1:82d25dc36295bc59cdf37af8e23c644a9c2e6aad Fix NULL value on OpenBSD when there is no acpitz0 2018-04-06T17:56:55+00:00 Florian Anderiasch fa@art-core.org 2018-04-06T17:54:12+00:00 urn:sha1:46b5c264d177f1e01bd17746071f4b0e1ca42eab Using %degrees on OpenBSD resulted in garbage values if sysctl doesn't know about any cpu temperature sensors. 2018-03-29T10:46:36+00:00 Dan Robertson dan.robertson@anidata.org 2017-03-22T00:39:49+00:00 urn:sha1:6a75ea9aea3bd7fd75d7c3e235b89586bbda4bdf If an address has been added with a label, ensure the correct address is shown. 2018-03-27T07:26:55+00:00 Ingo Bürk admin@airblader.de 2018-03-27T07:26:55+00:00 urn:sha1:4345fa9d9715a912c55828565783311e3fab4f0f 2018-03-27T07:07:53+00:00 Ingo Bürk admin@airblader.de 2018-03-27T07:07:53+00:00 urn:sha1:3aec438a5137e04c6e7952d3f9afd237002d1fda Remove overly aggressive #error 2018-02-12T13:12:04+00:00 Carlin Bingham cb@viennan.net 2018-02-12T13:12:04+00:00 urn:sha1:5b416d4ac00caf6028416999d3cef3b997d33f3b On some hardware the AUDIO_MIXER_READ ioctl requires the current number of channels to be set, and the mute device found needs to be checked if it belongs to the master output device. 2018-02-07T10:26:34+00:00 Gerome Fournier jef@foutaise.org 2018-02-07T10:26:34+00:00 urn:sha1:9212ee658bb977557f65f569336417a74f7c4edc 2018-01-28T14:37:51+00:00 johcgt 35880934+johcgt@users.noreply.github.com 2018-01-28T14:37:51+00:00 urn:sha1:d5c69a9d60a0bf9b6fbbaff7e122042410bfe44a `print_battery_info` computes `batt_info.percentage_remaining` by dividing batt_info.remaining by `full`. If `full` is `0` then the battery remaining will be reported as "inf". Before this, it tries to set `full` to either the design capacity or to the last known good charge. It determines if these values are available by checking whether their fields in `batt_info` are non-negative. As it initialized `batt_info` with values of `-1`, a non-negative value implies that something has provided a value. `slurp_all_batteries` and `add_battery_info` however initialize these fields to zero, so if these functions are called then `batt_info.full_design` will always be used. This means that on systems that don't provide a value for design capacity the percentage remaining will be reported as "inf", unless the user has set `last_full_capacity` to `true` in their `i3status.conf`. This patch changes `print_battery_info` to expect values for the battery capacity to be strictly greater than zero. This seems reasonable as a battery with a capacity of zero isn't useful. An alternative solution would be to change `slurp_all_batteries` and `add_battery_info` to initialize `batt_info` with `-1`, as `print_battery_info` does. This is less appealing as `add_battery_info` is accumulating the values, so using `-1` would introduce off-by-one errors without additional code to avoid them. 2017-12-11T11:16:00+00:00 Emeric Planet emeric.planet@datadoghq.com 2017-12-11T11:16:00+00:00 urn:sha1:657c0498dbc4eed26df8b7af1c87ea943c2bbdf6 2017-12-11T10:38:31+00:00 Emeric Planet emeric.planet@datadoghq.com 2017-12-11T10:38:31+00:00 urn:sha1:53fb9b4f18cd9ee3a64be5084ccc76aeea279515