jamesottaway / tmux-up Goto Github PK

Some users have muscle memory to launch tmux manually, and than want to think about how to structure their windows/panes. Running tmux-up $FILE when $TMUX is not empty should:

• rename the current session to what tmux-up calculates
• run tmux source-file $FILE

I think, skipping anything that starts with # (other than space like # comment) would be sufficient.

unknown command: #

For me the curl command used in README.md does not follow the redirect thus downloading a html document rather than the binary.

This would be a good place to store non-workspace related configurations.

For example, I can see myself having a bootstrap session for keeping the following tools up-to-date:

• nix
• fresh
• homebrew
• homebrew-cask

For workspaces which need have than one configuration, tmux-up can fall back to searching within the .tmux/ sub-directory if $1 cannot be found in the current working directory.

This would allow, for example, a workspace to maintain separate configurations for independent use cases, such as one for day-to-day development work and a different one for managing deployments.

In this case, if a primary configuration is generally preferred, it can be symlinked into the top-level working directory as .tmux.conf so tmux-up can still be invoked without any parameters.