The difference is that when iTerm2 quits or the ssh session is lost, tmux keeps running. An iTerm2 window opens and it acts like a normal iTerm2 window. When you run 'tmux -CC', a new tmux session is created. ITerm2's tmux integration solves these problems. Also, tmux's find feature isn't as good as iTerm2's.įor many users, a terminal multiplexer would be a great way to work, but they don't want to accept the drawbacks. Some built-in features of your terminal emulator don't work as well as they would if you weren't using tmux: for instance, you can't access tmux's scrollback history as easily or quickly as you can in a normal terminal window.

To adjust split panes, you have to enable mouse reporting, even if you don't want it otherwise.

You have to ssh to the remote host more than once to get more than one view of your tmux session's window.

Some keystroke must be dedicated to tmux to enter its command mode (^B, by default, which means moving the cursor to the left in emacs or an interactive shell becomes more difficult).

You can manipulate the environment by issuing commands to tmux. Normally, when you use tmux, multiple virtual windows are displayed in a single 'physical' window. ITerm2 is integrated with tmux, allowing you to enjoy a native user interface with all the benefits of tmux's persistence.

Tmux windows