-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
Read/write settings in XDG_CONFIG_HOME
#49
Comments
Thanks for the suggestion. But switching out the default settings folder now will likely break things for users that use the defaults (without explicitly specifying odmpy looks to an env var named One more thing that may not help much in your case, but if you use the same set of command options often, you can put them in a config file and reference it. odmpy libby @ex.conf |
I appreciate your commitment to stability. 😁 Assuming the default is currently your Either way, the env var should work for my purposes. Feel free to close this if it's not something you're interested in. |
I actually like your suggestion, so I'll keep this open until I can get around to working on it. |
This has been implemented on the master branch. |
Thank you! |
Closing because this is now available from the latest v0.8.0 release. |
Describe the problem
When using the
libby
commands, the token is written to the local folder. This is convenient if you only work in a single folder, but it would be nice if followed the (fairly standard) XDG Base Directory convention. So, the default settings config (if not specified; you could keep the flag) would be~/.config/odmpy
.You can put the settings there manually with the
--settings
flag, but it's annoying to type that for every operation.Version/Environment
The text was updated successfully, but these errors were encountered: