What does HackerNews think of tmux-resurrect?

Persists tmux environment across system restarts.

Language: Shell

Also check out tmux-resurrect to save and restore tmux window/pane config including working directories and scrollback. It can also restore running programs, which is sometimes a reasonable thing to do.

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

For anyone who's already using tmux and wants to persist their sessions across restarts, I cannot recommend tmux-resurrect and tmux-continuum highly enough.

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

> I might use a "save current layout as a template" command, I guess.

FWIW, this is available in tmux as a plugin. Very convenient and highly recommended.

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

I haven't tried Zellij, but it looks interesting. This is a great feature, and I think incorporating it into the base software reflects good UX priorities.

I use the `tmux-resurrect` plugin (https://github.com/tmux-plugins/tmux-resurrect) to restore my tmux session after a reboot. I highly recommend it.
Look into tmux-resurrect[0]. It allows you to save and restore tmux sessions, and an accept-list of running processes within those sessions. Ideally, you'd get the tmux session into the state you want re: windows, CWDs, running processes, etc., save it, and then restore from that session in the future.

[0] https://github.com/tmux-plugins/tmux-resurrect

> I reboot weekly, after which I have to re-arrange my work area, but once a week is OK.

You may want to have a look at Tmux resurrect[0]

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

Seems like a great idea. Lack of persistence bugs me about my i3 / tmux / emacs setup.

Google brings [1] but I haven't tried it yet.

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

I don't know the app you're talking about, but I solve this using persistent tmux sessions [1]. I use (Neo)Vim as my text editor, so it's just part of the tmux session. Each project has its own session.

I am aware that this doesn't really help you as your question seems to suggest you are not using an editor that can be run in the terminal.

[1] https://github.com/tmux-plugins/tmux-resurrect

>What takes a bit too long is setting it up again upon a restart.

Have you tried this tmux plugin? https://github.com/tmux-plugins/tmux-resurrect I use it all the time at work and at home

Should you have to reboot, this related tidbit can come in handy: https://github.com/tmux-plugins/tmux-resurrect
No. Mosh handles automatic reconnection (and a bunch of other stuff, like predictive typing so you don't notice flickering or slow connections, and performance improvements); tmux runs a persistent process on the remote side that preserves the state of your sessions.

Using mosh + tmux allows you to have both a) state persisted on the remote side, and b) automatic reconnects if your internet drops, or if you change connections. It's a very good combination, if you can handle some of the drawbacks of mosh (no in-terminal scrolling, mostly, but you can outsource that to tmux as well at the cost of a little lag).

A good additional piece of the puzzle is tmux-resurrect [1], which saves and automatically restores a lot of your tmux state to the filesystem so it's proof against power loss and system restarts/relogins. It persists window arrangements and similar, though it obviously can't save everything--the state of programs that were open can't be programmatically preserved (though that's getting closer and closer to seamless with the advent of things like CRIU).

The combination of mosh + tmux + tmux-resurrect is a very popular one and creates a very resilient system for "don't make me think; just log me in to my usual environment"-type systems, or environments where internet connectivity is spotty or the tmux server environment is unreliable or prone to rebooting.

[1] https://github.com/tmux-plugins/tmux-resurrect

Personally I use https://github.com/tmux-plugins/tmux-resurrect

It's not as configurable, but doesn't really need much configuration.

I haven't used it, but there's a plugin which allows for this behavior: https://github.com/tmux-plugins/tmux-resurrect
From https://leanpub.com/the-tao-of-tmux/read:

> Does tmux persist sessions after restarts?

I suggest mentioning tmux-resurrect: https://github.com/tmux-plugins/tmux-resurrect as this has made me far less grumpy about restarting a machine with many active tmux sessions. Save/Reload all your sessions, windows, panes, and layouts with a single shortcut key.

I use Tmux resurrect[1] with Tmux continuum[2] so that after rebooting my laptop, my tmux session is restored.

[1]: https://github.com/tmux-plugins/tmux-resurrect [2]: https://github.com/tmux-plugins/tmux-continuum

What you are looking for sounds a lot like TMUX + Bash (scripted tmux setup). Then you can run that inside of iTerm.

Tmux supports tabs and dynamic splits nicely via ncurses.

Also check out tmux ressurect [1] for saving tmux session persistence.

[1] https://github.com/tmux-plugins/tmux-resurrect

I've just published a tmux plugin that let's you save tmux environment and restore it later.

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