★ wanayoo — archive 1999 https://github.com/tmux-python/tmuxp/issues/475Nouvelle recherche | Portail wanayoo
Skip to content

/ tmuxp

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

Jump to bottom

Incorrect directory when XDG_CONFIG_DIR is set #475

Closed
sam-lunt opened this issue Feb 1, 2019 · 1 comment
Closed

Incorrect directory when XDG_CONFIG_DIR is set #475

sam-lunt opened this issue Feb 1, 2019 · 1 comment

Comments

@sam-lunt
Copy link

@sam-lunt sam-lunt commented Feb 1, 2019

When the XDG_USER_CONFIG variable is not set, tmuxp defaults to using ~/.config/tmuxp. ~/.config is a reasonable guess for XDG_USER_CONFIG (and I'd assume most people who've set XDG_USER_CONFIG have set it to be ~/.config). However, when XDG_USER_CONFIG is set, tmuxp doesn't do os.path.join(os.environ["XDG_USER_CONFIG"], "tmuxp"), instead it simply uses XDG_USER_CONFIG.

Is this difference intentional or just a minor oversight?
@sam-lunt
Copy link
Author

@sam-lunt sam-lunt commented Feb 1, 2019

To give a little more context, I have my tmuxp configuration files in ~/.tmuxp, but after updating tmuxp, I'm getting errors when I try to load a session. The reason for that is because I have XDG_USER_CONFIG set, causing tmuxp to look there for config files. Ideally, I'd like to place my config files in $XDG_USER_CONFIG/tmuxp, but it seems like I'd have to run tmuxp with XDG_USER_CONFIG unset for that to work.
@kstilwell kstilwell mentioned this issue May 14, 2019
Merged
@kstilwell kstilwell closed this May 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@kstilwell @sam-lunt
You can’t perform that action at this time.