Age | Commit message (Collapse) | Author |
|
Fixes #752
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
discharging
|
|
|
|
single BATT_STATUS_NAME macro. It simplifies customisation of the hard-wired status text.
|
|
|
|
|
|
|
|
This hopefully fixes http://bugs.i3wm.org/707
|
|
|
|
i3status (Thanks Artemis)
The former made i3bar crash, the latter is helpful for debugging.
|
|
It contradicts our philosophy and doesn’t work on many systems, so don’t use it
in the default config.
|
|
|
|
See also:
http://article.gmane.org/gmane.linux.kernel/1268792
The C compiler will handle (void) as "no arguments" and () as "variadic
function" (equivalent to (...)) which might lead to subtle errors.
|
|
FreeBSD), just emit a '?'.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
a2x.py
|
|
|
|
|
|
but works fine otherwise.
|
|
|
|
|
|
|
|
|
|
|
|
Otherwise, the separator is not properly interleaved with output.
|
|
|
|
This will make the script exit if i3bar has been killed or has crashed
instead of continuing to run in the background.
|
|
|