1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
|
i3status(1)
===========
Michael Stapelberg <michael+i3@stapelberg.de>
v2.2, September 2010
== NAME
i3status - Generates a status line for dzen2 or xmobar
== SYNOPSIS
i3status [-c configfile] [-h] [-v]
== OPTIONS
-c::
Specifies an alternate configuration file path. By default, i3status looks for
configuration files in the following order:
1. ~/.i3status.conf
2. ~/.config/i3status/config (or $XDG_CONFIG_HOME/i3status/config if set)
3. /etc/i3status.conf
4. /etc/xdg/i3status/config (or $XDG_CONFIG_DIRS/i3status/config if set)
== DESCRIPTION
i3status is a small program (less than 1000 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.
== CONFIGURATION
Since version 2, the configuration file for i3status will be parsed using
libconfuse. This makes configuration easier in the programmer’s point of
view and more flexible for the user at the same time.
The basic idea of i3status is that you can specify which "modules" should
be used (the order directive). You can then configure each module with its
own section. For every module, you can specify the output format. See below
for a complete reference.
.Sample configuration
-------------------------------------------------------------
general {
output_format = "dzen2"
colors = true
interval = 5
}
order = "ipv6"
order += "disk /"
order += "run_watch DHCP"
order += "run_watch VPN"
order += "wireless wlan0"
order += "ethernet eth0"
order += "battery 0"
order += "cpu_temperature 0"
order += "load"
order += "time"
wireless wlan0 {
format_up = "W: (%quality at %essid, %bitrate) %ip"
format_down = "W: down"
}
ethernet eth0 {
# if you use %speed, i3status requires the cap_net_admin capability
format_up = "E: %ip (%speed)"
format_down = "E: down"
}
battery 0 {
format = "%status %percentage %remaining"
}
run_watch DHCP {
pidfile = "/var/run/dhclient*.pid"
}
run_watch VPN {
pidfile = "/var/run/vpnc/pid"
}
time {
format = "%Y-%m-%d %H:%M:%S"
}
load {
format = "%5min"
}
cpu_temperature 0 {
format = "T: %degrees °C"
path = "/sys/devices/platform/coretemp.0/temp1_input"
}
disk "/" {
format = "%free"
}
-------------------------------------------------------------
=== General
The +colors+ directive will disable all colors if you set it to +false+. You can
also specify the colors that will be used to display "good", "degraded" or "bad"
values using the +color_good+, +color_degraded+ or +color_bad+ directives,
respectively. Those directives are only used if color support is not disabled by
the +colors+ directive. The input format for color values is the canonical RGB
hexadecimal triplet (with no separators between the colors), prefixed by a hash
character ("#").
*Example configuration*:
-------------------------------------------------------------
color_good = "#00FF00"
-------------------------------------------------------------
Likewise, you can use the +color_separator+ directive to specify the color that
will be used to paint the separator bar. The separator is always output in
color, even when colors are disabled by the +colors+ directive.
The +interval+ directive specifies the time in seconds for which i3status will
sleep before printing the next status line.
Using +output_format+ you can chose which format strings i3status should
use in its output. Currently available are:
dzen2::
Dzen is a general purpose messaging, notification and menuing program for X11.
It was designed to be scriptable in any language and integrate well with window
managers like dwm, wmii and xmonad though it will work with any windowmanger
xmobar::
xmobar is a minimalistic, text based, status bar. It was designed to work
with the xmonad Window Manager.
none::
Does not use any color codes. Separates values by the pipe symbol.
=== IPv6
This module gets the IPv6 address used for outgoing connections (that is, the
best available public IPv6 address on your computer).
*Example format_up*: +%ip+
*Example format_down* +no IPv6+
=== Disk
Gets used, free, available and total amount of bytes on the given mounted filesystem.
*Example order*: +disk /mnt/usbstick+
*Example format*: +%free (%avail)/ %total+
=== Run-watch
Expands the given path to a pidfile and checks if the process ID found inside
is valid (that is, if the process is running). You can use this to check if
a specific application, such as a VPN client or your DHCP client is running.
*Example order*: +run_watch DHCP+
=== Wireless
Gets the link quality and ESSID of the given wireless network interface. You
can specify different format strings for the network being connected or not
connected.
*Example order*: +wireless wlan0+
*Example format*: +W: (%quality at %essid, %bitrate) %ip+
=== Ethernet
Gets the IP address and (if possible) the link speed of the given ethernet
interface. Getting the link speed requires the cap_net_admin capability. Set
it using +setcap cap_net_admin=ep $(which i3status)+.
*Example order*: +ethernet eth0+
*Example format*: +E: %ip (%speed)+
=== Battery
Gets the status (charging, discharging, running), percentage and remaining
time of the given battery. If you want to use the last full capacity instead
of the design capacity (when using the design capacity, it may happen that
your battery is at 23% when fully charged because it’s old. In general, I
want to see it this way, because it tells me how worn off my battery is.),
just specify +last_full_capacity = true+.
*Example order*: +battery 0+
*Example format*: +%status %remaining+
=== CPU-Temperature
Gets the temperature of the given thermal zone.
*Example order*: +cpu_temperature 0+
*Example format*: +T: %degrees °C+
=== CPU Usage
Gets the percentual CPU usage from +/proc/stat+.
*Example order*: +cpu_usage+
*Example format*: +%usage+
=== Load
Gets the system load (number of processes waiting for CPU time in the last
5, 10 and 15 minutes).
*Example order*: +load+
*Example format*: +%5min %10min %15min+
=== Time
Formats the current system time. See +strftime(3)+ for the format.
*Example order*: +time+
*Example format*: +%Y-%m-%d %H:%M:%S+
=== DDate
Outputs the current discordian date in user-specified format. See +ddate(1)+ for
details on the format string.
*Note*: Neither *%.* nor *%X* are implemented yet.
*Example order*: +ddate+
*Example format*: +%{%a, %b %d%}, %Y%N - %H+
=== Volume
Outputs the volume of the specified mixer on the specified device. Works only
on Linux because it uses ALSA.
*Example order*: +volume master+
*Example format*: +♪: %volume+
*Example configuration*:
-------------------------------------------------------------
volume master {
format = "♪: %volume"
device = "default"
mixer = "Master"
mixer_idx = 0
}
-------------------------------------------------------------
== Using i3status with dzen2
After installing dzen2, you can directly use it with i3status. Just ensure that
+output_format+ is set to +dzen2+.
*Example for usage of i3status with dzen2*:
--------------------------------------------------------------
i3status | dzen2 -fg white -ta r -w 1280 \
-fn "-misc-fixed-medium-r-normal--13-120-75-75-C-70-iso8859-1"
--------------------------------------------------------------
== Using i3status with xmobar
To get xmobar to start, you might need to copy the default configuration
file to +~/.xmobarrc+. Also, ensure that the +output_format+ option for i3status
is set to +xmobar+.
*Example for usage of i3status with xmobar*:
---------------------------------------------------------------------
i3status | xmobar -o -t "%StdinReader%" -c "[Run StdinReader]"
---------------------------------------------------------------------
== SEE ALSO
+strftime(3)+, +date(1)+, +glob(3)+, +dzen2(1)+, +xmobar(1)+
== AUTHORS
Michael Stapelberg and contributors
Thorsten Toepper
Baptiste Daroussin
|
