For example, iTerm or Terminator are already capable of multiplexing a terminal. This makes more sense for the local environment, when you decide to supercharge your terminal emulator, which otherwise does not support aforementioned features.

Terminal multiplexing, named windows, split window into several panes.We should clarify to ourselves why we need this “nested tmux in tmux” thing, because at first glance it looks pretty crazy. Featuresįirst let’s quickly go through tmux features and advantages, to understand their relevance to local or remote scenarios. If you’re curious how it all works together, continue reading. Nested tmux remote sessions happily coexist even in side-by-side panes in local tmux session The bottom pane with the Ubuntu14 remote session is further split into 2 panes, and we have 3 windows: shell, mon, and logs. The “zsh” window is split into 2 panes: in both panes we SSH’ed to the remote hosts (CentOS7 and Ubuntu14) and jump into remote tmux sessions there. The local session has 2 windows: “zsh” and “node”. We have a local tmux session on OSX inside iTerm2 (run in full screen mode). It is about using and configuring tmux v2, local and remote tmux sessions usage, and how to support a scenario when a remote tmux session is going to be nested inside a local tmux session.īefore you start reading, here is a working example from my machine.

This is the first part of my tmux in practice article series. By Alexey Samoshkin Tmux in practice: local and nested remote tmux sessions We discuss tmux features, their relevance for local and remote scenarios, and how to setup and configure tmux to support nested sessions

Tmux custom status bar