3 Michael Stapelberg <michael@i3wm.org>
8 i3status - Generates a status line for i3bar, dzen2, xmobar or lemonbar
12 i3status [-c configfile] [-h] [-v]
17 Specifies an alternate configuration file path. By default, i3status looks for
18 configuration files in the following order:
20 1. ~/.config/i3status/config (or $XDG_CONFIG_HOME/i3status/config if set)
21 2. /etc/xdg/i3status/config (or $XDG_CONFIG_DIRS/i3status/config if set)
27 i3status is a small program (about 1500 SLOC) for generating a status bar for
28 i3bar, dzen2, xmobar, lemonbar or similar programs. It is designed to be very
29 efficient by issuing a very small number of system calls, as one generally
30 wants to update such a status line every second. This ensures that even under
31 high load, your status bar is updated correctly. Also, it saves a bit of energy
32 by not hogging your CPU as much as spawning the corresponding amount of shell
37 The basic idea of i3status is that you can specify which "modules" should
38 be used (the order directive). You can then configure each module with its
39 own section. For every module, you can specify the output format. See below
40 for a complete reference.
43 -------------------------------------------------------------
45 output_format = "dzen2"
52 order += "run_watch DHCP"
53 order += "run_watch VPNC"
54 order += "path_exists VPN"
55 order += "wireless wlan0"
56 order += "ethernet eth0"
58 order += "cpu_temperature 0"
60 order += "tztime local"
61 order += "tztime berlin"
64 format_up = "W: (%quality at %essid, %bitrate) %ip"
65 format_down = "W: down"
69 # if you use %speed, i3status requires the cap_net_admin capability
70 format_up = "E: %ip (%speed)"
71 format_down = "E: down"
75 format = "%status %percentage %remaining %emptytime"
76 format_down = "No battery"
80 status_full = "☻ FULL"
81 path = "/sys/class/power_supply/BAT%d/uevent"
86 pidfile = "/var/run/dhclient*.pid"
90 # file containing the PID of a vpnc process
91 pidfile = "/var/run/vpnc/pid"
95 # path exists when a VPN tunnel launched by nmcli/nm-applet is active
96 path = "/proc/sys/net/ipv4/conf/tun0"
100 format = "%Y-%m-%d %H:%M:%S"
104 format = "%Y-%m-%d %H:%M:%S %Z"
105 timezone = "Europe/Berlin"
113 format = "T: %degrees °C"
114 path = "/sys/devices/platform/coretemp.0/temp1_input"
120 -------------------------------------------------------------
124 The +colors+ directive will disable all colors if you set it to +false+. You can
125 also specify the colors that will be used to display "good", "degraded" or "bad"
126 values using the +color_good+, +color_degraded+ or +color_bad+ directives,
127 respectively. Those directives are only used if color support is not disabled by
128 the +colors+ directive. The input format for color values is the canonical RGB
129 hexadecimal triplet (with no separators between the colors), prefixed by a hash
132 *Example configuration*:
133 -------------------------------------------------------------
134 color_good = "#00FF00"
135 -------------------------------------------------------------
137 Likewise, you can use the +color_separator+ directive to specify the color that
138 will be used to paint the separator bar. The separator is always output in
139 color, even when colors are disabled by the +colors+ directive. This option has
140 no effect when +output_format+ is set to +i3bar+ or +none+.
142 The +interval+ directive specifies the time in seconds for which i3status will
143 sleep before printing the next status line.
145 Using +output_format+ you can chose which format strings i3status should
146 use in its output. Currently available are:
149 i3bar comes with i3 and provides a workspace bar which does the right thing in
150 multi-monitor situations. It also comes with tray support and can display the
151 i3status output. This output type uses JSON to pass as much meta-information to
152 i3bar as possible (like colors, which blocks can be shortened in which way,
155 Dzen is a general purpose messaging, notification and menuing program for X11.
156 It was designed to be scriptable in any language and integrate well with window
157 managers like dwm, wmii and xmonad though it will work with any windowmanger
159 xmobar is a minimalistic, text based, status bar. It was designed to work
160 with the xmonad Window Manager.
162 lemonbar is a lightweight bar based entirely on XCB. It has full UTF-8 support
163 and is EWMH compliant.
165 Use ANSI Escape sequences to produce a terminal-output as close as possible to
166 the graphical outputs. This makes debugging your config file a little bit
167 easier because the terminal-output of i3status becomes much more readable, but
168 should only used for such quick glances, because it will only support very
169 basic output-features (for example you only get 3 bits of color depth).
171 Does not use any color codes. Separates values by the pipe symbol by default.
172 This should be used with i3bar and can be used for custom scripts.
174 It's also possible to use the color_good, color_degraded, color_bad directives
175 to define specific colors per module. If one of these directives is defined
176 in a module section its value will override the value defined in the general
177 section just for this module.
179 If you don't fancy the vertical separators between modules i3status/i3bar
180 uses by default, you can employ the +separator+ directive to configure how
181 modules are separated. You can either disable the default separator altogether
182 setting it to the empty string. You might then define separation as part of a
183 module's format string. This is your only option when using the i3bar output
184 format as the separator is drawn by i3bar directly otherwise. For the other
185 output formats, the provided non-empty string will be automatically enclosed
186 with the necessary coloring bits if color support is enabled.
188 i3bar supports Pango markup, allowing your format strings to specify font
189 color, size, etc. by setting the +markup+ directive to "pango". Note that the
190 ampersand ("&"), less-than ("<"), greater-than (">"), single-quote ("'"), and
191 double-quote (""") characters need to be replaced with "`&`", "`<`",
192 "`>`", "`'`", and "`"`" respectively. This is done automatically
193 for generated content (e.g. wireless ESSID, time).
195 *Example configuration*:
196 -------------------------------------------------------------
198 output_format = "xmobar"
206 format = "[ load: %1min, %5min, %15min ]"
211 -------------------------------------------------------------
215 This module gets the IPv6 address used for outgoing connections (that is, the
216 best available public IPv6 address on your computer).
218 *Example format_up*: +%ip+
220 *Example format_down*: +no IPv6+
224 Gets used, free, available and total amount of bytes on the given mounted filesystem.
226 These values can also be expressed in percentages with the percentage_used,
227 percentage_free, percentage_avail and percentage_used_of_avail formats.
229 Byte sizes are presented in a human readable format using a set of prefixes
230 whose type can be specified via the "prefix_type" option. Three sets of
231 prefixes are available:
234 IEC prefixes (Ki, Mi, Gi, Ti) represent multiples of powers of 1024.
237 SI prefixes (k, M, G, T) represent multiples of powers of 1000.
239 The custom prefixes (K, M, G, T) represent multiples of powers of 1024.
241 It is possible to define a low_threshold that causes the disk text to be
242 displayed using color_bad. The low_threshold type can be of threshold_type
243 "bytes_free", "bytes_avail", "percentage_free", or "percentage_avail", where
244 the former two can be prepended by a generic prefix (k, m, g, t) having
245 prefix_type. So, if you configure low_threshold to 2, threshold_type to
246 "gbytes_avail", and prefix_type to "binary", and the remaining available disk
247 space is below 2 GiB, it will be colored bad. If not specified, threshold_type
248 is assumed to be "percentage_avail" and low_threshold to be set to 0, which
249 implies no coloring at all.
251 You can define a different format with the option "format_not_mounted"
252 which is used if the path does not exist or is not a mount point. So you can just empty
253 the output for the given path with adding +format_not_mounted=""+
254 to the config section.
256 *Example order*: +disk /mnt/usbstick+
258 *Example format*: +%free (%avail)/ %total+
260 *Example format*: +%percentage_used used, %percentage_free free, %percentage_avail avail+
262 *Example prefix_type*: +custom+
264 *Example low_threshold*: +5+
266 *Example threshold_type*: +percentage_free+
270 Expands the given path to a pidfile and checks if the process ID found inside
271 is valid (that is, if the process is running). You can use this to check if
272 a specific application, such as a VPN client or your DHCP client is running.
273 There also is an option "format_down". You can hide the output with
276 *Example order*: +run_watch DHCP+
278 *Example format*: +%title: %status+
282 Checks if the given path exists in the filesystem. You can use this to check if
283 something is active, like for example a VPN tunnel managed by NetworkManager.
284 There also is an option "format_down". You can hide the output with
287 *Example order*: +path_exists VPN+
289 *Example format*: +%title: %status+
293 Gets the link quality, frequency and ESSID of the given wireless network
294 interface. You can specify different format strings for the network being
295 connected or not connected.
297 The special interface name `_first_` will be replaced by the first wireless
298 network interface found on the system (excluding devices starting with "lo").
300 *Example order*: +wireless wlan0+
302 *Example format*: +W: (%quality at %essid, %bitrate / %frequency) %ip+
306 Gets the IP address and (if possible) the link speed of the given ethernet
307 interface. Getting the link speed requires the cap_net_admin capability. Set
308 it using +setcap cap_net_admin=ep $(which i3status)+.
310 The special interface name `_first_` will be replaced by the first non-wireless
311 network interface found on the system (excluding devices starting with "lo").
313 *Example order*: +ethernet eth0+
315 *Example format*: +E: %ip (%speed)+
319 Gets the status (charging, discharging, unknown, full), percentage, remaining
320 time and power consumption (in Watts) of the given battery and when it's
321 estimated to be empty. If you want to use the last full capacity instead of the
322 design capacity (when using the design capacity, it may happen that your
323 battery is at 23% when fully charged because it’s old. In general, I want to
324 see it this way, because it tells me how worn off my battery is.), just specify
325 +last_full_capacity = true+. You can hide seconds in the remaining time and
326 empty time estimations by setting +hide_seconds = true+.
328 If you want the battery percentage to be shown without decimals, add
329 +integer_battery_capacity = true+.
331 If your battery is represented in a non-standard path in /sys, be sure to
332 modify the "path" property accordingly, i.e. pointing to the uevent file on
333 your system. The first occurence of %d gets replaced with the battery number,
334 but you can just hard-code a path as well.
336 It is possible to define a low_threshold that causes the battery text to be
337 colored red. The low_threshold type can be of threshold_type "time" or
338 "percentage". So, if you configure low_threshold to 10 and threshold_type to
339 "time", and your battery lasts another 9 minutes, it will be colored red.
341 Optionally custom strings including any UTF-8 symbols can be used for different
342 battery states. This makes it possible to display individual symbols
343 for each state (charging, discharging, unknown, full)
344 Of course it will also work with special iconic fonts, such as FontAwesome.
345 If any of these special status strings are omitted, the default (CHR, BAT, UNK,
348 *Example order*: +battery 0+
350 *Example format*: +%status %remaining (%emptytime %consumption)+
352 *Example format_down*: +No battery+
354 *Example status_chr*: +⚡ CHR+
356 *Example status_bat*: +🔋 BAT+
358 *Example status_unk*: +? UNK+
360 *Example status_full*: +☻ FULL+
362 *Example low_threshold*: +30+
364 *Example threshold_type*: +time+
366 *Example path*: +/sys/class/power_supply/CMB1/uevent+
370 Gets the temperature of the given thermal zone. It is possible to
371 define a max_threshold that will color the temperature red in case the
372 specified thermal zone is getting too hot. Defaults to 75 degrees C.
374 *Example order*: +cpu_temperature 0+
376 *Example format*: +T: %degrees °C+
378 *Example max_threshold*: +42+
380 *Example path*: +/sys/devices/platform/coretemp.0/temp1_input+
384 Gets the percentual CPU usage from +/proc/stat+ (Linux) or +sysctl(3)+
387 It is possible to define a max_threshold that will color the load
388 value red in case the CPU average over the last interval is getting
389 higher than the configured threshold. Defaults to 95.
391 It is possible to define a degraded_threshold that will color the load
392 value yellow in case the CPU average over the last interval is getting
393 higher than the configured threshold. Defaults to 90.
395 *Example order*: +cpu_usage+
397 *Example format*: +%usage+
399 *Example max_threshold*: +75+
401 *Example degraded_threshold*: +25+
405 Gets the system load (number of processes waiting for CPU time in the last
406 1, 5 and 15 minutes). It is possible to define a max_threshold that will
407 color the load value red in case the load average of the last minute is
408 getting higher than the configured threshold. Defaults to 5.
410 *Example order*: +load+
412 *Example format*: +%1min %5min %15min+
414 *Example max_threshold*: +"0,1"+
418 Outputs the current time in the local timezone.
419 To use a different timezone, you can set the TZ environment variable,
420 or use the +tztime+ module.
421 See +strftime(3)+ for details on the format string.
423 *Example order*: +time+
425 *Example format*: +%Y-%m-%d %H:%M:%S+
429 Outputs the current time in the given timezone.
430 If no timezone is given, local time will be used.
431 See +strftime(3)+ for details on the format string.
432 The system's timezone database is usually installed in +/usr/share/zoneinfo+.
433 Files below that path make for valid timezone strings, e.g. for
434 +/usr/share/zoneinfo/Europe/Berlin+ you can set timezone to +Europe/Berlin+
435 in the +tztime+ module.
437 *Example order*: +tztime berlin+
439 *Example format*: +%Y-%m-%d %H:%M:%S %Z+
441 *Example timezone*: +Europe/Berlin+
443 If you would like to use markup in this section, there is a separate
444 +format_time+ option that is automatically escaped. Its output then replaces
445 %time in the format string.
447 *Example configuration (markup)*:
448 -------------------------------------------------------------
450 format = "<span foreground='#ffffff'>time:</span> %time"
451 format_time = "%H:%M %Z"
452 timezone = "Europe/Berlin"
454 -------------------------------------------------------------
458 Outputs the current discordian date in user-specified format. See +ddate(1)+ for
459 details on the format string.
460 *Note*: Neither *%.* nor *%X* are implemented yet.
462 *Example order*: +ddate+
464 *Example format*: +%{%a, %b %d%}, %Y%N - %H+
468 Outputs the volume of the specified mixer on the specified device. PulseAudio
469 and ALSA (Linux only) are supported. If PulseAudio is absent, a simplified
470 configuration can be used on FreeBSD and OpenBSD due to the lack of ALSA, the
471 +device+ and +mixer+ options can be ignored on these systems. On these systems
472 the OSS API is used instead to query +/dev/mixer+ directly if +mixer_idx+ is
473 -1, otherwise +/dev/mixer++mixer_idx+.
475 To get PulseAudio volume information, one must use the following format in the
484 where N is the index of the PulseAudio sink. If no sink is specified the
485 default is used. If the device string is missing or is set to "default",
486 PulseAudio will be tried if detected and will fallback to ALSA (Linux)
487 or OSS (FreeBSD/OpenBSD).
489 *Example order*: +volume master+
491 *Example format*: +♪: %volume+
493 *Example format_muted*: +♪: 0%%+
495 *Example configuration*:
496 -------------------------------------------------------------
498 format = "♪: %volume"
499 format_muted = "♪: muted (%volume)"
504 -------------------------------------------------------------
505 *Example configuration (PulseAudio)*:
506 -------------------------------------------------------------
508 format = "♪: %volume"
509 format_muted = "♪: muted (%volume)"
512 -------------------------------------------------------------
514 == Universal module options
516 When using the i3bar output format, there are a few additional options that
517 can be used with all modules to customize their appearance:
520 The alignment policy to use when the minimum width (see below) is not
521 reached. Either +center+ (default), +right+ or +left+.
523 The minimum width (in pixels) the module should occupy. If the module takes
524 less space than the specified size, the block will be padded to the left
525 and/or the right side, according to the defined alignment policy. This is
526 useful when you want to prevent the whole status line from shifting when
527 values take more or less space between each iteration.
528 The option can also be a string. In this case, the width of the given text
529 determines the minimum width of the block. This is useful when you want to
530 set a sensible minimum width regardless of which font you are using, and at
531 what particular size. Please note that a number enclosed with quotes will
532 still be treated as a number.
534 A boolean value which specifies whether a separator line should be drawn
535 after this block. The default is true, meaning the separator line will be
536 drawn. Note that if you disable the separator line, there will still be a
537 gap after the block, unless you also use separator_block_width.
538 separator_block_width::
539 The amount of pixels to leave blank after the block. In the middle of this
540 gap, a separator symbol will be drawn unless separator is disabled. This is
541 why the specified width should leave enough space for the separator symbol.
543 *Example configuration*:
544 -------------------------------------------------------------
550 separator_block_width = 1
552 -------------------------------------------------------------
554 == Using i3status with dzen2
556 After installing dzen2, you can directly use it with i3status. Just ensure that
557 +output_format+ is set to +dzen2+.
559 *Example for usage of i3status with dzen2*:
560 --------------------------------------------------------------
561 i3status | dzen2 -fg white -ta r -w 1280 \
562 -fn "-misc-fixed-medium-r-normal--13-120-75-75-C-70-iso8859-1"
563 --------------------------------------------------------------
565 == Using i3status with xmobar
567 To get xmobar to start, you might need to copy the default configuration
568 file to +~/.xmobarrc+. Also, ensure that the +output_format+ option for i3status
571 *Example for usage of i3status with xmobar*:
572 ---------------------------------------------------------------------
573 i3status | xmobar -o -t "%StdinReader%" -c "[Run StdinReader]"
574 ---------------------------------------------------------------------
576 == What about memory usage or CPU frequency?
578 While talking about two specific things, please understand this section as a
579 general explanation why your favorite information is not included in i3status.
581 Let’s talk about memory usage specifically. It is hard to measure memory in a
582 way which is accurate or meaningful. An in-depth understanding of how paging
583 and virtual memory work in your operating system is required. Furthermore, even
584 if we had a well-defined way of displaying memory usage and you would
585 understand it, I think that it’s not helpful to repeatedly monitor your memory
586 usage. One reason for that is that I have not run out of memory in the last few
587 years. Memory has become so cheap that even in my 4 year old notebook, I have
588 8 GiB of RAM. Another reason is that your operating system will do the right
589 thing anyway: Either you have not enough RAM for your workload, but you need to
590 do it anyway, then your operating system will swap. Or you don’t have enough
591 RAM and you want to restrict your workload so that it fits, then the operating
592 system will kill the process using too much RAM and you can act accordingly.
594 For CPU frequency, the situation is similar. Many people don’t understand how
595 frequency scaling works precisely. The generally recommended CPU frequency
596 governor ("ondemand") changes the CPU frequency far more often than i3status
597 could display it. The display number is therefore often incorrect and doesn’t
598 tell you anything useful either.
600 In general, i3status wants to display things which you would look at
601 occasionally anyways, like the current date/time, whether you are connected to
602 a WiFi network or not, and if you have enough disk space to fit that 4.3 GiB
605 However, if you need to look at some kind of information more than once in a
606 while (like checking repeatedly how full your RAM is), you are probably better
607 off with a script doing that, which pops up an alert when your RAM usage reaches
608 a certain threshold. After all, the point of computers is not to burden you
609 with additional boring tasks like repeatedly checking a number.
611 == External scripts/programs with i3status
613 In i3status, we don’t want to implement process management again. Therefore,
614 there is no module to run arbitrary scripts or commands. Instead, you should
615 use your shell, for example like this:
617 *Example for prepending the i3status output*:
618 --------------------------------------------------------------
620 # shell script to prepend i3status with more stuff
625 echo "mystuff | $line" || exit 1
627 --------------------------------------------------------------
629 Put that in some script, say +.bin/my_i3status.sh+ and execute that instead of i3status.
631 Note that if you want to use the JSON output format (with colors in i3bar), you
632 need to use a slightly more complex wrapper script. There are examples in the
633 contrib/ folder, see http://code.i3wm.org/i3status/tree/master/contrib
637 When receiving +SIGUSR1+, i3status’s nanosleep() will be interrupted and thus
638 you will force an update. You can use killall -USR1 i3status to force an update
639 after changing the system volume, for example.
643 +strftime(3)+, +date(1)+, +glob(3)+, +dzen2(1)+, +xmobar(1)+
647 Michael Stapelberg and contributors
655 Fernando Tarlá Cardoso Lemos