Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Source config files from ./.tmux/ #6

Open
jamesottaway opened this issue Mar 16, 2015 · 1 comment
Open

Source config files from ./.tmux/ #6

jamesottaway opened this issue Mar 16, 2015 · 1 comment

Comments

@jamesottaway
Copy link
Owner

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.

poxar added a commit to poxar/tmux-up that referenced this issue Mar 20, 2015
@poxar
Copy link
Contributor

poxar commented Mar 20, 2015

One could place all the configurations in the top level as hidden files for the same effect. Since the dot gets stripped away anyway, the behaviour should be the same, or am I missing something?

Having a .tmux/ sub-directory makes sense, if you want to avoid file clutter though. But then I'd argue, that we should also try to load the default .tmux.conf from there. For example as .tmux/tmux.conf. I have a branch, that implements this. It's based on #7 though, so I won't open a pull request just yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants