-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add configuration path command-line option #6161
Comments
Commented by: daschuer Hi Jens, |
Commented by: jenszo Hi Daniel, I think I can have it finished by the end of next week. It is more
Best, Am 20.01.2012 00:23, schrieb Daniel Schürmann:
|
Commented by: jenszo Am 20.01.2012 10:22, schrieb Jens Nachtigall:
Sorry, realistically I cannot make this happen in due time. Please I am happy to test and review the code if you have somthing. regards, |
Commented by: daschuer The attached patch introduces the --settingsPath command line option. |
Commented by: daschuer The attached patch is an update for lp:mixxx #2988 |
Commented by: daschuer commited to lp:mixxx/1.11 #3306 |
Commented by: d00guan A small bug. Controllers should be loaded from resource path, not settingsPath |
Commented by: rryan Thanks for catching that Anders -- committed your fix to lp:mixxx/1.11 r3313. |
Issue closed with status Fix Released. |
Reported by: Pegasus-RPG
Date: 2011-12-01T06:25:49Z
Status: Fix Released
Importance: Wishlist
Launchpad Issue: lp898487
Attachments: settingsPath.patch, settingsPath2.patch, [Additional patch with fixed path](https://bugs.launchpad.net/bugs/898487/+attachment/3219004/+files/Additional patch with fixed path)
As suggested by nachtigall on the forums:
For those of us that both gig out with Mixxx and test/develop it, it would be handy to have a --configPath command-line parameter (that defaulted to ~/.mixxx as usual if not specified) so we can easily keep the profiles separate without having to copy & rename directories every time. This would be especially handy for storing the profile on removable media.
The text was updated successfully, but these errors were encountered: