i3status is a small program for generating a status bar for -i3bar, dzen2, xmobar, lemonbar 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.
i3status is a small program for generating a status bar for i3bar, dzen2, +xmobar, lemonbar 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.
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 +
Using output_format you can choose which format strings i3status should use in its output. Currently available are:
If you don’t fancy the vertical separators between modules i3status/i3bar uses by default, you can employ the separator directive to configure how -modules are separated. You can either disable the default separator altogether +modules are separated. You can also disable the default separator altogether by setting it to the empty string. You might then define separation as part of a module’s format string. This is your only option when using the i3bar output format as the separator is drawn by i3bar directly otherwise. For the other output formats, the provided non-empty string will be automatically enclosed with the necessary coloring bits if color support is enabled.
i3bar supports Pango markup, allowing your format strings to specify font +
i3bar supports Pango markup, allowing your format strings to specify font, color, size, etc. by setting the markup directive to "pango". Note that the ampersand ("&"), less-than ("<"), greater-than (">"), single-quote ("'"), and double-quote (""") characters need to be replaced with "&", "<", @@ -399,17 +398,20 @@ connected or not connected.
The special interface name _first_ will be replaced by the first wireless network interface found on the system (excluding devices starting with "lo").
Example order: wireless wlan0
Example format: W: (%quality at %essid, %bitrate / %frequency) %ip
Example format_up: W: (%quality at %essid, %bitrate / %frequency) %ip
Example format_down: W: down
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).
The special interface name _first_ will be replaced by the first non-wireless network interface found on the system (excluding devices starting with "lo").
Example order: ethernet eth0
Example format: E: %ip (%speed)
Example format_up: E: %ip (%speed)
Example format_down: E: down
It is possible to define a degraded_threshold that will color the load value yellow in case the CPU average over the last interval is getting -higher than the configured threshold. Defaults to 90. The output format +higher than the configured threshold. Defaults to 90. The output format when above degraded threshold can be customized with format_above_degraded_threshold.
For displaying the Nth CPU usage, you can use the %cpu<N> format string, +starting from %cpu0. This feature is currently not supported in FreeBSD.
Example order: cpu_usage
Example format: %usage
Example format: all: %usage CPU_0: %cpu0 CPU_1: %cpu1
Example max_threshold: 75
Example format_above_threshold: Warning above threshold: %usage
Example degraded_threshold: 25