I am going to associate this with #51, so the freezer can have tests against handling IO situations like this.

This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Thank you
for your contributions.

This bot is used to handle issues where the issue hasn't been discussed or
has gone out of date. If an issue isn't resolved and handled in a certain
period of time, it may be closed. If you would like your issue re-opened,
please create a fresh issue with the latest, up to date information and
mention this issue in it.

How do we reopen this?

@sakalys Reopened

Currently, if you attempt to freeze and save the config to an existing file, then you are informed that you cannot do so, because the file already exists. I am willing to code and submit a pull request that would allow the tmuxp freeze command to overwrite the specified file.

Does anyone see any problems with this, because I did not look anywhere else in the code except the function responsible for the command?

Facing the same need here, it'd be great if tmuxp freeze could just overwrite an existing session.

I mean, yeah I could automate the deletion and then tmuxp freeze again, but that seems like an unnecessary workaround.

BTW, thanks for 'tmuxp'! It's the icing on the cake of my bash/vim/EmacsOrgmode/tmux workflow!

Cheers