Empowering your tmux (status bar) experience!
tmux-powerline is a tmux tpm plugin that gives you a slick and hackable powerline status bar consisting of segments. It's easily extensible with custom segments and themes. The plugin itself is implemented purely in bash thus minimizing system requirements. However you can make segments in any language you want (with a shell wrapper).
Some examples of segments available that you can add to your tmux status bar are (full list here):
- LAN & WAN IP addresses
- Now Playing for MPD, Spotify (GNU/Linux native or wine, macOS), iTunes (macOS), Rhythmbox, Banshee, MOC, Audacious, Rdio (macOS), cmus, Pithos and Last.fm (last scrobbled track).
- New mail count for GMail, Maildir, mbox, mailcheck, and Apple Mail
- GNU/Linux and macOS battery status (uses richo/dotfiles/bin/battery)
- Weather in Celsius, Fahrenheit and Kelvin using Yahoo Weather
- System load, cpu usage and uptime
- Git, SVN and Mercurial branch in CWD
- Date and time
- Hostname
- tmux info
- tmux mode indicator (normal/prefix, mouse, copy modes)
- CWD in pane
- Current X keyboard layout
- Network download/upload speed
- Earthquake warnings
Full screenshot
left-status
Current tmux session, window and pane, hostname and LAN & WAN IP address.
right-status
New mails, now playing, average load, weather, date and time.
Now I've read my inbox so the mail segment disappears!
After pausing the music there's no need for showing the Now Playing segment anymore. Also the weather has become much nicer!
Laptop mode: a battery segment.
dual-line status
@xx4h is helping out developing, maintaining and managing this project!
Requirements for the lib to work are:
tmux -V>= 2.1bash --version>= 3.2 (Does not have to be your default shell.)- Nerd Font. Follow instructions at Font Installation. However you can use other substitute symbols as well; see
config.sh.
Some segments have their own requirements. If you enable them in your theme, make sure all requirements are met for those.
wan_ip.sh,now_playing.sh(last.fm),weather_yahoo.sh: curl, bcnow_playing.sh- mpd: libmpdclient
- last.fm:
jq
xkb_layout.sh: X11, XKBmailcount.sh(gmail): wget, (mailcheck): mailcheck.ifstat.sh: ifstat (there is a simpler segment not using ifstat but samples /sys/class/net)tmux_mem_cpu_load.sh: tmux-mem-cpu-loadrainbarf.sh: rainbarfweather.sh: GNUgrepwith Perl regular expression enabled (FreeBSD specific),jqfor yrno weather API.
Preinstalled grep in FreeBSD doesn't support Perl regular expressions. Solution is rather simple -- you need to use textproc/gnugrep port instead. You also need to make sure, that it has support for PCRE and is compiled with --enable-perl-regexp flag.
- Install tpm and make sure it's working.
- Install tmux-powerline as a plugin by adding a line to
tmux.conf:set -g @plugin 'erikw/tmux-powerline' - Install the plugin with
<prefix>I, unless you changed tpm's keybindings.- The default powerline should already be visible now!
- Continue to the Configuration section below.
Note that tpm plugins should be at the bottom of you tmux.conf. This plugin will then override some tmux settings like status-left, status-right etc. If you had already set those in your tmux config, it is a good opportunity to remove or comment those out.
Take a look at main.tmux for exactly which settings are overridden.
tmux-powerline stores the custom config, themes and segments at $XDG_CONFIG_HOME/tmux-powerline/.
To make the following example easier, let's assume the following:
$XDG_CONFIG_HOMEhas the default value of~/.config- tmux-powerline was installed to the XDG path
~/.config/tmux/plugins/tmux-powerline
Adapt the commands below if your paths differs from this.
Start by generating your own configuration file:
~/.config/tmux/plugins/tmux-powerline/generate_config.sh
mv ~/.config/tmux-powerline/config.sh.default ~/.config/tmux-powerline/config.sh
$EDITOR ~/.config/tmux-powerline/config.shGo through the default config and adjust to your needs!
The theme is specified by setting the environment variable $TMUX_POWERLINE_THEME in the config file above. It will use a default theme and you probably want to use your own. The default config have set the custom theme path to be ~/.config/tmux-powerline/themes/.
Make a copy of the default theme and make your own, say my-theme:
mkdir -p ~/.config/tmux-powerline/themes
cp ~/.config/tmux/plugins/tmux-powerline/themes/default.sh ~/.config/tmux-powerline/themes/my-theme.sh
$EDITOR ~/.config/tmux-powerline/themes/my-theme.shRemember to update the configuration file to use the new theme by setting TMUX_POWERLINE_THEME=my-theme
In the same was as themes, you can create your own segments at TMUX_POWERLINE_DIR_USER_SEGMENTS which defaults to ~/.config/tmux-powerline/segments.
To get started, copy an existing segment that is similar to the segment that you want to create.
mkdir -p ~/.config/tmux-powerline/segments
cp ~/.config/tmux/plugins/tmux-powerline/segments/date.sh ~/.config/tmux-powerline/segments/my-segment.sh
$EDITOR ~/.config/tmux-powerline/segments/my-segment.shNow you can add my-segment to your own theme!
Also see How to make a segment below for more details.
Some segments might not work on your system for various reasons such as missing programs or different versions not having the same options. To find out which segment is not working it may help to enable the debug setting in ~/.config/tmux-powerline/config.sh.
However this may not be enough to determine the error so you can inspect all executed bash commands (will be a long output) by doing
bash -x powerline.sh (left|right)To debug smaller portions of code, say if you think the problem lies in a specific segment, insert these lines at the top and bottom of the relevant code portions e.g. inside a function:
set -x
exec 2>/tmp/tmux-powerline.log
<code to debug>
set +xand then inspect the outputs like
less /tmp/tmux-powerline.log
tail -f /tmp/tmux-powerline.log # or follow output like this.You can also enable the debug mode in your config file. Look for the TMUX_POWERLINE_DEBUG_MODE_ENABLED environment variable and set it to true.
If you can not solve the problems you can post an issue and be sure to include relevant information about your system and script output (from bash -x) and/or screenshots if needed. Be sure to search in the resolved issues section for similar problems you're experiencing before posting.
You have edited ~/.tmux.conf but no powerline is displayed. This might be because tmux is not aware of the changes so you have to restart your tmux session or reloaded that file by typing this on the command-line (or in tmux command mode with prefix :)
tmux source-file ~/.tmux.confIf your tmux looks like this then you may have to in iTerm uncheck [Unicode East Asian Ambiguous characters are wide] in Preferences -> Settings -> Advanced.
This project can only gain positively from contributions. Fork today and make your own enhancements and segments to share back! If you'd like, add your name and email to AUTHORS before making a pull request so you can get some credit for your work :-)
If you want to (of course you do!) send a pull request for a cool segment you written make sure that it follows the style of existing segments, unless you have good reason for it. Each segment resides in the segments/ directory with a descriptive and simple name.
A segment must have at least one function and that is run_segment which is like the main function that is called from the tmux-powerline lib. What ever text is echoed out from this function to stdout is the text displayed in the tmux status bar.
If the segment at a certain point does not have anything to show, simply don't echo anything out and the segment will be hidden. A successful execution of the run_segment function should return an exit code of 0.
If the segment failed to execute in a fatal way return a non-zero exit code so the user can pick up the error and fix it when debug mode is on (e.g. missing program that is needed for the segment).
Usage of helper function to organize the work of a segment is encourage and should be named in the format __helper_func. If a segment has settings it should have a function generate_segmentrc which outputs default values of all settings and a short
explanation of the setting and its values. Study e.g. segments/now_playing.sh to see how it is done. A segment having settings should typically call a helper function __process_settings as the first statement in run_segment that sets default values
to the settings that has not been set by the user.
Also, don't use bash4 features as requiring bash4 complicates installation for macOS user quite a bit. Use tabs for indentation (discussion),
I have another tmux plugin that might interest you:
- tmux-dark-notify - A plugin that make tmux's theme follow macOS dark/light mode.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent