DEV Community

Discussion on: Devs, why do you use terminal tabs over tmux windows?

Collapse
 
val_baca profile image
Valentin Baca • Edited

Command+#: one key combo, muscle memory (browser tabs use the same shortcut), native so it's near instant, can easily pull tabs out and move to another window, move into another window, or put side-by-side

Ctrl-b, #: two key combo, not-native (there's a lag equal to the tmux timeout)

To me: tmux does not have much use for terminals on my local machine.

I use tmux for any remote host, but locally tmux doesn't provide me anything. The only thing I'm worried about is my Mac giving a kernel panic. Tmux doesn't protect against that.

Vim can save sessions. My shell keeps my history, which I can Ctrl-r to search back through (P.S. adding a #comment to shell commands really helps with this). My paths are kept short or I use symlinks to quickly get back to where I need to be. I write scripts.

BTW iTerm has tmux integration so that iTerm tabs == tmux tabs. Just add -CC to any tmux commands.

Collapse
 
maxdevjs profile image
maxdevjs

my Mac giving a kernel panic. Tmux doesn't protect against that

A couple plugins help with such catastrophic scenario:

tmux-plugins/tmux-resurrect
tmux-plugins/tmux-continuum

Tried a couple times to check if it'd work, and it did as expected.

Restoring vim and neovim sessions never needed it, so no clues on how effective it is.