[Aeolun]

Tmux on my local machine was useless. Tmux on my server has been a godsent. Just connect and re-attach to the tmux session and you are right where you left off.

I did modify the key binds a little bit to make splitting windows and enable the mouse, but otherwise I just don’t need any more advanced behavior.

[ghshephard]

I guess different work patterns work differently for different people. I've been using tmux exclusively on my local machine (much less often on remote machines) for the last 2+ years, and it really works well for me. On a daily basis I tend to work in a lot of different contexts, so having scroll-back buffer and bash history nicely organized so I can switch from task to task, with clean restoration of the scrollback/bash history for each environment when I reboot my computer to update it is a godsend. I also like having the various parallel running tasks for a particular environment (like an ssh, log tail, commands) - all running in different panes in a single window - so I never have to go looking for them.

One change I made was forcing myself to always name a window when it gets created - that way I can usually hotkey back into an environment by its name, rather than having to go searching for windows.

I particularly like that I can use exactly the same toolset on my Mac, Windows, and Linux clients.

[julienchastang]

"Tmux on my server has been a godsent." Exactly. I let my cloud VM tmux sessions run for months. I manage other VMs and Docker containers from my tmux "command center".

[dllthomas]

I use a terminal multiplexer (happens to be screen, but could as easily be tmux) to manage local contexts. A fresh terminal in the same context is then just three keys away. The contexts drive a number of things, but most importantly I set BASH_HISTFILE so each has its own history. I love it, but of course ymmv.