Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Freeze overwrite and persistence of original file settings #921

vlappa started this conversation in Ideas
Discussion options

I was attempting to create a default tmuxp.json file when it doesn't exists on a specific location. Then make tmuxp freeze overwrite that file. What I didn't realize was that all the default values, initially set, are now gone of course, it's a complete new file.

For my use case it would be nice if the settings like environment and before_script, which are not available in the current freezed session would persist.

There are probably better ways to do this, like sending tmux keys etc.

You're welcome to think with me...

You must be logged in to vote

Replies: 1 comment 1 reply

Comment options

A solution for the environment is to set the environment first and then load with the append option, where the sessionName is the same as configured in the yaml/json file. You can also start with a dedicated server socket

tmux -L customSocketName new -e FOO=bar -s sessionName tmuxp load -L customSocketName --append file.tmuxp.json

You must be logged in to vote
1 reply
Comment options

This doesn't work when the session is created by tmux first it seems.

I would like to create a detached session with tmux and then attach and append to that session with a tmuxp configuration / json file.

tmux -L customSocketName new -e FOO=bar -s sessionName

tmuxp load -L customSocketName --append file.tmuxp.json

 raise exc.TmuxSessionExists(
libtmux.exc.TmuxSessionExists: Session named sessionName exists
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Ideas
Labels
None yet
1 participant

AltStyle によって変換されたページ (->オリジナル) /