10 Commits

Author	SHA1	Message	Date
dcoppa	21469b28e1	In the configuration file, remove comments from the wireless stanza, ... since wireless monitoring now works fine. While here, add a message about how to deal with the configuration of i3status. ok jasper@	2012-10-12 07:57:26 +00:00
jasper	dd671692ea	make it possible to get temperature readings from devices other than acpitz. ... use the 'path' option in your configuration's cpu_temperature block to e.g. cpu0.	2012-10-09 16:02:07 +00:00
jasper	b49e4e3a8f	- change the default (and since the API is still limiting us here, only) ... device from which we read temperature values from, from cpu(4) to acpitz(4).	2012-10-09 13:19:48 +00:00
jasper	e96bb59820	s/quality/signal/ found the hard way by rpe@	2012-10-09 09:32:26 +00:00
jasper	e9aa0d3a41	- use %speed in the default config	2012-10-09 09:08:12 +00:00
jasper	ba35faa86c	- give an example for the cpu_temperature.	2012-10-08 11:49:30 +00:00
jasper	7950fed04e	- update to i3status 2.6 ... tested by dcoppa@ also	2012-10-04 06:15:38 +00:00
dcoppa	db76844826	Set output_format to "i3bar", to have colours by default. ... ok jasper@ (maintainer)	2012-09-27 11:06:31 +00:00
jasper	b113616306	- update to 2.5.1	2012-05-14 07:54:23 +00:00
jasper	864f7b3978	import i3status 2.4.1 (git clone as of a few days ago, along with a load of ... patches for OpenBSD support, which have all been committed upstream already) i3status is a small program (about 1500 SLOC) for generating a status bar for dzen2, xmobar or similar programs. It is designed to be very efficient by issuing a very small number of system calls, as one generally wants to update such a status line every second. This ensures that even under high load, your status bar is updated correctly. Also, it saves a bit of energy by not hogging your CPU as much as spawning the corresponding amount of shell commands would. ok dcoppa@	2012-05-02 07:37:10 +00:00