8
2
I currently switched to iTerm2 + VIM for my dev environment. I noticed that the last version of iTerm2 supports tmux
and there were people using tmux
to split the window into several sessions. I also noticed that iTerm2 has options out of the box to split the window into several sessions. You can split as many sessions as you want vertically and horizontally by just using CMD+D for example. So to me it seems that you can accomplish the same functionality with those options. I could be totally wrong.
My questions is: Is there a difference/benefit by using tmux
over the splitting options on iTerm2?
Thanks akira! that was my very first question on SU and received a great answer, just exactly what I needed! – wonitta – 2012-03-09T07:29:31.200
Isn't the process hierarchy more like:
iterm2 > shell > tmux client
andtmux server > shell
? So when you close iTerm, you close the tmux client but the server is still around. – Henrik N – 2012-03-18T21:11:12.930@HenrikN: iTerm2 might call the tmux-client "directly". you would get the same effect if you launch "exec tmux attach" or something similar. and yes, tmux consists of 2 parts. but that distinction does not improve the understanding why iterm2-splitting is different from tmux-splitting, does it? – akira – 2012-03-19T07:31:54.267
@akira I just wanted to clear it up because you put tmux under iTerm, which perhaps makes it harder to see how tmux survives when the iTerm process exits. To me, the best way to understand that is to realize that the tmux server is independent of iTerm (but the client is not). But certainly, the fact that tmux and not iterm owns the split shells is a key point. – Henrik N – 2012-03-19T08:14:11.473