Option to kill 0 session

[ain]

Use-case:

1. Restarting a machine
2. tmux
3. Restore

What happens: sessions restored, but there's a 0 session, the 1st one that launched in step 2.

What could happen: with some smart configuration flag, that 0 session could be killed during the restore, it's clutter.

[nesl247]

Ah, so it wasn't just something odd that I was doing. I thought I had done something wrong.

[ain]

I'd change this feature idea also to incorporate a command line tool, e.g. tmux-resurrect that would start tmux, restore and explicitly kill the 0 session once done.

[paulhybryant]

hi, I have the same issue and this is what I use to achieve what you need here:

In .tmux.conf, add the following line in the end
if-shell '[[ $(tmux list-sessions | wc -l ) -eq 0 ]]' 'run-shell $HOME/.tmux/plugins/tmux-resurrect/scripts/restore.sh'

create an alias, e.g. alias tmux-start='tmux start-server; tmux attach'
Then when use tmux-start and no dummy session will be created, with all your saved sessions resurrected.

Hope that helps.

Thanks,

[ain]

I think it's a good direction, but it's failing in the scenario where there're no sessions so tmux attach would simply throw no sessions and exit.

[paulhybryant]

Yeah, you should only use the alias tmux-start when you saved your session.
Otherwise just use tmux as usual.

[soyuka]

After restoring it could:

//go to second session if first is 0 
tmux attach-session -t $(tmux list-session | head -n 1 | awk '{print $1}')
//delete first one
tmux kill-session -t 0

[paulhybryant]

In my case it is slightly different. The session created after restoring is
not "0", but "4" (because I have three saved sessions).
So relying on killing the session with name "0" is a bit unreliable.

On Sat, Dec 12, 2015 at 3:41 AM, Antoine Bluchet notifications@github.com
wrote:

After restoring it could:

//go to second session if first is 0
tmux attach-session -t $(tmux list-session | head -n 1 | awk '{print $1}')
//delete first one
tmux kill-session -t 0

—
Reply to this email directly or view it on GitHub
#101 (comment)
.

With Regards,

Yu Huang

Software Engineer,
Google Inc.

[unhammer]

Is there not a way to start tmux and at the same time send in a command to be run?

[paulhybryant]

IIUC, what you want can be done by including the command you want to run
when server is being started in .tmux.conf

On Wed, Jan 20, 2016 at 12:00 AM, Kevin Brubeck Unhammer <
notifications@github.com> wrote:

Is there not a way to start tmux and at the same time send in a command to
be run?

—
Reply to this email directly or view it on GitHub
#101 (comment)
.

With Regards,

Yu Huang

Software Engineer,
Google Inc.

[janzenz]

Whew! I've been banging my head with this and thought I was the only one having this issue. The problem with tmux start-server solution is that as of tmux 2.2 this command doesn't run the server by default unless there's a session running. See this issue

[cedricpim]

Any solutions to this, for tmux 2.2?

[damokuro]

If you're using tmux-resurrect, you can just edit the plugin yourself to do so. In .tmux/plugins/tmux-resurrect/scripts/restore.sh insert a tmux kill-session at the end of the main() function after the restoration being completed, like so:

		display_message "Tmux restore complete!"
		tmux kill-session
	fi
}
main

This will kill the current session you're in, so the one from which you restored tmux sessions. Do NOT use this if you restore from sessions you still plan on using.

[kaykayehnn]

Since hooks were added in #267 a simple solution for this is adding set -g @resurrect-hook-pre-restore-pane-processes 'tmux switch-client -n && tmux kill-session -t=0' to tmux.conf.

Just keep in mind that session 0 will be killed even if it was one of the restored sessions. This shouldn't be a problem if you name your sessions.

[rollf]

I have tmux-continuum installed and launch tmux by tmux a. This does not create an "empty" session.