Tmux configuration, that supercharges your tmux and builds cozy and cool terminal environment.
Status line widgets:
Personally, I use it on OSX 10.11.5 El Capitan through iTerm2.
On OSX you can install latest 2.6 version with
brew install tmux. On Linux it's better to install from source, because official repositories usually contain outdated version. For example, CentOS7 - v1.8 from base repo, Ubuntu 14 - v1.8 from trusty/main. For how to install from source, see this gist or just google it.
To install tmux-config:
$ git clone https://github.com/samoshkin/tmux-config.git $ ./tmux-config/install.sh
install.sh script does following:
~/.tmux.confwill be backed up
~/.tmux/plugins/tpm, unless already presemt
Finally, you can jump into a new tmux session:
$ tmux new
Windows and pane indexing starts from
1 rather than
0. Scrollback history limit is set to
20000. Automatic window renameing is turned off. Aggresive resizing is on. Message line display timeout is
1.5s. Mouse support in
# parent terminal $ echo $TERM xterm-256color # jump into a tmux session $ tmux new $ echo $TERM screen-256color
~/.tmux.conf overrides default key bindings for many action, to make them more reasonable, easy to recall and comforable to type.
Let's go through them.
If you are an iTerm2 user, third column describes the keybinding of similar "action" in iTerm2. It's possible to reuse very same keys you already get used to and tell iTerm2 to execute analogous tmux actions. See iTerm2 and tmux integration section below.
|tmux key||Description||iTerm2 key|
||Default prefix, used instead of "C-b". Same prefix is used in screen program, and it's easy to type. The only drawback of "C-a" is that underlying shell does not receive the keystroke to move to the beginning of the line.||-|
||Open ~/.tmux.conf file in your $EDITOR||-|
||Reload tmux configuration from ~/.tmux.conf file||-|
||Rename current window||-|
||Rename current session||-|
||Split new pane horizontally||⌘⇧D|
||Split new pane vertically||⌘D|
||Select next pane||⌘[|
||Select previous pane||⌘]|
||Select pane on the left||⌘⌥←|
||Select pane on the right||⌘⌥→|
||Select pane on the top||⌘⌥↑|
||Select pane on the bottom||⌘⌥↓|
||Resize pane to the left||^⌘←|
||Resize pane to the right||^⌘→|
||Resize pane to the top||^⌘↑|
||Resize pane to the bottom||^⌘↓|
||Move to next window||⌘⇧]|
||Move to previous window||⌘⇧[|
||Switch to most recently used window||^Tab|
||Link window from another session by entering target session and window reference||-|
||Swap panes back and forth with 1st pane. When in main-horizontal or main-vertical layout, the main panel is always at index 1. This keybinding let you swap secondary pane with main one, and do the opposite.||⌘\|
||Swap current active pane with next one||-|
||Toggle zoom for current pane||⌘⇧Enter|
||Kill current pane||⌘W|
||Kill current window||⌘⌥W|
||Kill other windows but current one (with confirmation)||-|
||Kill current session (with confirmation)||-|
||Merge current session with another. Essentially, this moves all windows from current session to another one||-|
||Detach from session||-|
||Detach other clients except current one from session||-|
||Toggle status bar visibility||-|
||Monitor current window for activity||-|
||Monitor current window for silence by entering silence period||-|
||Switch off all key binding and prefix hanling in current window. See "Nested sessions" paragraph for more info||-|
I've started with Powerline as a status line, but then realized it's too fat for my Macbook 15'' display, it hardly can fit all those fancy arrows, widgets and separators, so that I can only see one window "tab".
So I decide to make my feet wet, with the idea to keep it dense, and include essential widgets. Sometimes it tries to replicate OSX topbar (battery, date time).
The left part contains only current session name.
Window tabs use Powerline arrows glyphs, so you need to install Powerline enabled font to make this work. See Powerline docs for instructions and here is the collection of patched fonts for powerline users
The right part of status line consists of following components:
You might want to hide status bar using
<prefix> C-s keybinding.
One prefers using tmux on local machine to supercharge their terminal emulator experience, other use it only for remote scenarios to retain session/state in case of disconnect. Things are getting more complex, when you want to be on both sides. You end up with nested session, and face the question: How you can control inner session, since all keybindings are caught and handled by outer session?. Community provides several possible solutions.
The most common is to press
C-a prefix twice. First one is caught by local session, whereas second is passed to remote one. Nothing extra steps need to be done, this works out of the box. However, root keytable bindings are still handled by outer session, and cannot be passed to inner one.
Second attempt to tackle this issue, is to setup 2 individual prefixes,
C-b for local session, and
C-a for remote session. And, you know, it feels like:
And finally accepted solution, turn off all keybindings and key prefix handling in outer session, when working with inner one. This way, outer session just sits aside, without interfering keystrokes passed to inner session. Credits to http://stahlke.org/dan/tmux-nested/ and this Github issue
So, how it works. When in outer session, simply press
F12 to toggle off all keybindings handling in outer session. Now work with inner session using the same keybinding scheme and same keyprefix. Press
F12 to turn on outer session back.
You might notice that when key bindings are "OFF", special
[OFF] visual indicator is shown in the status line, and status line changes its style (colored to gray).
Remote session is detected by existence of
$SSH_CLIENT variable. When session is remote, following changes are applied:
You can apply remote-specific settings by extending
There are some tweaks to copy mode and scrolling behavior, you should be aware of.
There is a root keybinding to enter Copy mode:
M-Up. Once in copy mode, you have several scroll controls:
Space starts selection,
Enter copies selection and exits copy mode. List all items in copy buffer using
prefix C-p, and paste most recent item from buffer using
y just copies selected text and is equivalent to
Y copies whole line, and
D copies by the end of line.
Also, note, that when text is copied any trailing new lines are stripped. So, when you paste buffer in a command prompt, it will not be immediately executed.
You can also select text using mouse. Default behavior is to copy text and immediately cancel copy mode on
MouseDragEnd event. This is annoying, because sometimes I select text just to highlight it, but tmux drops me out of copy mode and reset scroll by the end. I've changed this behavior, so
MouseDragEnd does not execute
copy-selection-and-cancel action. Text is copied, but copy mode is not cancelled and selection is not cleared. You can then reset selection by mouse click.
When you copy text inside tmux, it's stored in private tmux buffer, and not shared with system clipboard. Same is true when you SSH onto remote machine, and attach to tmux session there. Copied text will be stored in remote's session buffer, and not shared/transported to your local system clipboard. And sure, if you start local tmux session, then jump into nested remote session, copied text will not land in your system clipboard either.
This is one of the major limitations of tmux, that you might just decide to give up using it. Let's explore possible solutions:
All solutions above are suitable for sharing tmux buffer with system clipboard for local machine scenario. They still does not address remote session scenarios. What we need is some way to transport buffer from remote machine to the clipboard on the local machine, bypassing remote system clipboard.
There are 2 workarounds to address remote scenarios.
Use ANSI OSC 52 escape sequence to talk to controlling/parent terminal and pass buffer on local machine. Terminal should properly undestand and handle OSC 52. Currently, only iTerm2 and XTerm support it. OSX Terminal, Gnome Terminal, Terminator do not.
Second workaround is really involved and consists of local network listener and SSH remote tunneling:
ssh -R 2222:localhost:3333 [email protected]
echo "buffer" | nc localhost 2222
2222on remote machine to port
3333on local machine.
3333, and pipes any input to
This tmux-config does its best to integrate with system clipboard, trying all solutions above in order, and falling back to OSC 52 ANSI escape sequences in case of failure.
On OSX you might need to install
brew install reattach-to-user-namespace, and make sure OSC 52 sequence handling is turned on in iTerm. (Preferences -> General -> Applications in Terminal may access clipboard).
On Linux, make sure
xsel is installed. For remote scenarios, you would still need to setup network listener and use SSH remote tunneling, unless you terminal emulators supports OSC 52 sequences.
All colors related to theme are declared as variables. You can change them in
# This is a theme CONTRACT, you are required to define variables below # Change values, but not remove/rename variables itself color_dark="$color_black" color_light="$color_white" color_session_text="$color_blue" color_status_text="colour245" color_main="$color_orange" color_secondary="$color_purple" color_level_ok="$color_green" color_level_warn="$color_yellow" color_level_stress="$color_red" color_window_off_indicator="colour088" color_window_off_status_bg="colour238" color_window_off_status_current_bg="colour254"
Note, that variables are not extracted to dedicated file, as it should be, because for some reasons, tmux does not see variable values after sourcing
theme.conf file. Don't know why.
If you're an iTerm use same to me, most likely you already have a muscle memory for most common actions and keybindings (split pane, focus pane, fullscreen pane, move between tabs, create new tab, etc). When I switched to tmux, I found new key table more difficult: more keys to type, don't forget to enter
prefix and recall if you've already pressed it or not (compare
C-a, c with "⌘T", or
C-a -> with "⌘⌥->"). iTerm2 keybinding was so natural to me, so I decided to remap most common keybindings to tell iTerm2 to execute corresponding tmux actions.
You can setup new profile in iTerm preferences to override default keybindings, to tell iTerm to send pre-configured sequences of keys, that will trigger corresponding action in tmux.
For example, when "^⌘↑" pressed, sequence of bytes
0x01 0x1b 0x5b 0x31 0x3b 0x35 0x41 are sent through terminal to running tmux instance, that interprets them as
C-a C-↑ keybinding and triggers
resize-pane -U according to our
You can get binary representation of any keys, using
$od -t x1 ^A^[[1;5A // press C-a C-↑ on your keyboard 0000000 01 1b 5b 31 3b 35 41 0000007
$ showkey -a Press any keys - Ctrl-D will terminate this program ^A 1 0001 0x01 ^[[1;5A 27 0033 0x1b 91 0133 0x5b 49 0061 0x31 59 0073 0x3b 53 0065 0x35 65 0101 0x41
You can remap whatever key in this way, but I do this only for those ones, which have similar analogous action in tmux and are most common(resize pane, zoom pane, create new window, etc). See table with keybindings above.
As additional step, you can setup this new iTerm profile as default one, and tell it to jump into tmux session right off the start.
You can then go full screen in iTerm, so iTerm tabs and frame do not distract you (anyway now you're using iTerm just as a tunnel to your tmux, everything else happens inside tmux).