This is built on top of tmux-continuum & tmux-resurrect, tmux plugins which I've been using now for 10+ years - pretty much every day - they bring so much joy to using tmux.
Zero worries about having to restore local window settings - It's not uncommon for me to have 40+ panes split across 15+ windows. Windows / Dell / Security updates have me rebooting almost weekly - which means a restart of WSL - but, with continuum/ressurect - zero issues - all the windows, panes, scrollback (!) and with just a tiny bit of bash history foo - command history - are completely restored as though nothing had changed.
Really interested to see if restore lives up the foundations that it's built on.
Except... any running process?
> Windows / Dell / Security updates have me rebooting almost weekly - which means a restart of WSL
Oh the irony of WSL being a VM but not leveraging VM snapshotting capabilities.
You can configure certain commands to re-run, including certain subcommands.
My previous list looks a little like this:
'ssh psql mysql sqlite3 atuin btop lazysql lazygit lazydocker "~mt start->mt start " "~mt sh->mt sh " "git reflog" "git adog" "git log" "~cargo run->cargo run " syncthing mosh "~devpod ssh->devpod ssh "
So SSH or mosh would reconnect, database connections would reestablish. TUI programs like atuin, btop, lazysql, lazygit, and lazydocker would restore.
mt start was my custom command to orchestrate containers at work, so that would start up. Then some git commands that don't do anything such as git log.