tmux-resurrect VS Mosh

I use https://github.com/tmux-plugins/tmux-continuum and https://github.com/tmux-plugins/tmux-resurrect to restore all my tmux sessions if I reboot my machine or kill tmux.

tmux-resurrect and tmux-continuum are the utils I use to persist sessions across reboots. They have keybinds and options to make it either automatic or manual, but they save EVERYTHING down to the Neovim session (if you use those) for the session's working directory

This would be my first go-to: https://github.com/tmux-plugins/tmux-resurrect

I hardly reboot a machine unless I am intending to, but there are plugins for tmux for this too.

https://github.com/tmux-plugins/tmux-resurrect

And to save and restore tmux sessions automatically, I use tmux-resurrect + tmux-continuum.

You must use all 3 of: tmux-continuum tmux-resurrect vim-obsession

Sure. Once you log in to the remote Linux machine, just run `tmux` and do your job. When you connect to the remote Linux machine next time, run `tmux attach`, and you will be right where you left off. The sessions will be persisted until you restart the Linux machine (well, or kill the tmux server). If you'd like even more persistence after machine restart, you can also try https://github.com/tmux-plugins/tmux-resurrect

If you haven’t already, and I know this doesn’t hold up for GUI emacs or vim, but consider running them through https://mosh.org/

FWIW, I wouldn't try to parse escape sequences "directly" from the input bytestream -- it's easy to end up with annoying bugs. Longer-term it's probably better to separate the logic e.g.:

- First step (for a UTF-8-input terminal emulator) means "lexing" the input bytestream as UTF-8 into a stream of USVs, which involves some subtleties (https://github.com/mobile-shell/mosh/blob/master/src/termina...).

- Second step is to run the DEC parser/FSM logic on the sequence of USVs, which is independent of the escape sequences (https://vt100.net/emu/dec_ansi_parser ; https://github.com/mobile-shell/mosh/blob/master/src/termina...).

- And then the third step is for the terminal to execute the "dispatch"/"execute"/etc. actions coming from the FSM, which is where the escape sequences and control chars get implemented (https://github.com/mobile-shell/mosh/blob/master/src/termina...).

Without this separation, it's easier to end up with bugs where, e.g., a UTF-8 sequence or an ANSI escape sequence is treated differently when it's split between multiple read() calls vs. all in one call.

Btw, you can use mosh to hide the latency of SSH. https://mosh.org/

I've been using Kitty's SSH features for as long as I can remember but I recently setup Mosh and I really like how it doesn't drop connections and supports roaming.

I am surprised many people write about ssh into a server. Mosh[1] feels more responsive and it also supports longer sessions.

[1] - https://mosh.org/

Also they support Mosh which I install on my servers. It's way better than plain ssh when you're on mobile networks and wifi, especially with connections that are unreliable or bandwidth-constrained.

I’ve recently been experimenting with MoSH (Mobile Shell). Basically think SSH but with UDP - so more resilient to shoddy network conditions, roaming access points, etc.

If it is not for production (e.g. running as a daemon or a server) and you only care about the development, another ad-hoc way is using screen/tmus-like software incl. byobu, and combine it with mosh.