tmux-continuum VS auto-session

tmux has these 2 plugins to add the auto-save/restore functionality:

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

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

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

tmux-resurrect is my most important one, and thanks for mentioning tmux-continuum, which is new to me.

I use tmux-continuum for that. Works really well. What are you missing?

Checkout here: https://github.com/tmux-plugins/tmux-continuum

The plugins are: https://github.com/goolord/alpha-nvim and https://github.com/rmagatti/auto-session

I use auto-session for session management and session-lens telescope extension for switching the sessions. When I switch to a different session, auto-session clears all buffers from my current session, including the modified ones, without warning. I'm wondering if there are any ways to prevent losing my changes. For instance, can I save the modified buffers in the session and load them on session restore, or configure auto-session to give me a warning before switching to a new session if there are unsaved changes? Alternatively, is there a way to use Telescope to display a list of recently modified buffers, so that I can review them before switching sessions and take appropriate action?

buffers: I open and close nvim instances all day long, using https://github.com/rmagatti/auto-session (or one of the many other session management plugins), it saves my buffers on a per git branch basis, so I lose nothing. nvim opens in less than a second, so this is no burden at all.

Yes, I use rmagatti/auto-session with some gnarly hacks to save a subset of window options, a per-session colorscheme, and some other wacky stuff so it stays 99.9% the same between sessions.

The correct one is : auto-session (I edited the mistake in the message above)

auto-session ?

I'm also using auto-session and nvim-tree which can both interact with the session.

Finally, to save sessions and move through them, check: auto-session

Yes, for this purpose, I'm using rmagatti/auto-session