I've thought about switching to tmux for all the nice features it has but to be honest I stick with GNU Screen because it's built in. I rarely spend much time on the same server, I tend to hop machine to machine a lot in my job. So installing and configuring new software starts to take up a lot of time, and most of the servers I use are client servers, not mine.

Same thing with vim customizations or bashrc files. I learn to love the defaults and fit my workflow around them because in two months I'll be on another server and would have to reconfigure everything to fit my workflow otherwise.

I use tmux regularly, especially on headless servers to which I am SSHing over an unreliable channel (meaning any given SSH app on my iPad that is likely to time out if I switch away from it for too long, or the Doctor's assistant calls my name and I have to lock the screen).

It's extra useful when I am doing something that takes a long time, like upgrading from Debian 8 to 9 with apt-get, and losing the connection would be a real pain.

I used to use GNU screen, but tmux - for me - proved more reliable, and much easier to set up for sharing a screen with a different user to help debug or learn something.

The keystroke mappings don't bother me, and as a hard-core command-line user, I totally appreciate the switch from Ctrl-a (aka "go to start of line") to Ctrl-b. Hitting Ctrl-a while trying to edit a command line and nothing - or worse - happening can be super frustrating, and not all term types support Home and End.

I also just use a small subset of the commands and use 'Ctrl-b ?' if I forget.

So a big thumbs up for tmux from me.

It's great, once you remap CTRL-B to CTRL-A.

I personally only really use it to tile, and navigate between, 3 or 4 shells when developing, but it's delightful for that (much better than using e.g. Ctrl-Tab to flip between terminals for me). I also second the recommendation of switching to use Ctrl-A.

I love it, after a few remaps (am far too used to ctrl+a to move around). Combined with Powerline[1] it's one of the first things I open. I have two aliases for convenience so that I can easily name and attach to sessions.

    ta='tmux attach -t'
    tc='tmux new -s'

[1] https://github.com/powerline/powerline

I used to use Screen due to the argument that it's always installed but instead I just install a few things by default on systems I work on and haven't looked back (same with zsh vs bash).

I may have misused or misunderstood tmux in the past.

Honestly I'd rather just open another cygwin/terminal window. Every OS already does windowing really well. If I have a long running process, then ctrl-z, bg, fg work perfectly fine too. tmux seemed too complicated to be worth the effort to learn.

I tried it, but I didn't see the point, since I was already using a tiling WM. And I can configure the shortcuts for my WM whereas with tmux I have to learn all the specific shorcuts.

It's brilliant. Unlike the others I only use it for my local development, but tmux + vim (or any editor) + scripts and tools makes for the best IDE available.

the session saver plugin is great. combine that with vim sessions and it basically saves all my context across reboots.