The author recommends learning about session management before digging into the window management side of things, which I think is reasonable. One software suite that makes that a little easier is abduco + dvtm, which are designed to work together, but don’t need to be, and separately handle the session management and multiplexing (respectively) that tmux/screen couple together. I am not an avid user because I haven’t found the great need for any of the above quite yet, but I found them very helpful in demystifying what tmux is supposed to be so great for.
Thanks for the links. Factoring tmux out into abduco/dvtm does seem conceptually nice, and clarifies the building blocks of what tmux is doing. Although if I were to always use them as a pair I’m not sure there’d be a big practical advantage to them being separate binaries. Seems like the advantage would come if I were to sometimes use just one or the other on its own.
In case someone hasn’t heard of it, Mosh is a replacement for ssh that is designed with the intention of the workflow described in the article (working in a session on a remote machine).
I have personally stopped using tmux after getting used to neovim and its terminal mode. It is not perfect, but I like having one less layer to manage.
Do people have any guidelines on dealing with nested tmuxes? I often find that I use a tmux locally and one when I ssh. The trouble is keybindings on remote servers aren’t always detected. For example, it’s hard to make says S-left arrow work to move between terminals on the remote end.
Perhaps similar to this:
I find that when I want to interact with the inner tmux, I have to ^B, count to 1, ^B whatever. If you’re too fast, the outer tmux slurps it up.