tmux (and screen) are incredible assets for remote sessions, both for continuity across dropped shells and multi-shell activities when the connection process is tedious (multiple jumphosts, proxies, etc.)

▲

jauntywundrkind 5 days ago | parent | next [-]

I've fallen out of using it, but for a while I was using dtach to do similar without the virtual terminal multiplexing. Much much more direct.

I'd just run a vim session. If I needed terminals, they were in my vim! Even wrote a short shell-script to automate creating or re-attaching to a project specific vim session. https://github.com/jauntywunderkind/dtachment

Haven't looked into it, but I'm love a deeper nvim + atuin (shell history) integration.

▲

iiyama 4 days ago | parent [-]

It might be quite similar window/tab managing functionality, but for me it's the same thing that made me choose tmux over screen: it comes with a nice status bar as default and hotkeys are somehow easier to memorize.

	▲	jauntywundrkind a day ago \| parent [-]
		My dtach+nvim uses nvim as terminal multiplexer & "status bar", which is pretty ok! Dtach only serves as a very very dumb pass through (where-as tmux really is a persistent virtual terminal that clients can read-out from).

▲

o11c 5 days ago | parent | prev [-]

The continuity benefit is much less than it used to be, now that we have systemd with `enable-linger` so we can make proper daemons.

▲

em-bee 5 days ago | parent [-]

that's not what tmux provides continuity for. the continuity is for interactive sessions. on my server i have more than 20 tmux windows, each one for one specific purpose. they have been running for several years.

	▲	o11c 4 days ago \| parent [-]
		My point is that a lot of hysterical-raisin interactive sessions really don't need to be.