bat-extras VS tmux-resurrect

So it seems that clone3 is the syscall that creates new threads. Let's use man (better if you use batman) to find about it.

If you like bat, you may find these useful: https://github.com/eth-p/bat-extras#batman

for man pager I found and absolutely love batman (from the amazing bat extras by eth-p

Idea: Look into adding color to it. After discovering batman I've become used to syntax highlighted man pages.

Next, there is bat and one of its add-ons: batman which provides git diff support, syntax highlighting and vim-style navigation on top of the base command of cat and man.

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