Open nickbe opened 6 years ago
This is a really good point, and I'll admit I haven't toyed with portability myself yet. I would definitely regard it as a higher-than-average priority. Any ideas about this particular workaround @sallar?
We had planned to release a purely portable version (#429), but that hasn't taken root yet.
Well it IS rather simple for windows. Since you're writing the data to the APPDATA folder, the only question is: how do you get the APPDATA path in the first place? If you switch to evaluating the APPDATA environment variable the the batch above would just work fine and we'd have a portable version very easily 😁
I've accepted this as an issue, as it would be a great feature to have. I currently don't have time to implement right now but PRs are welcome.
I'd like to keep the buttercup installation on a usb stick. Buttercup seems to evaluate the APPDATA environment variable and store its configuration folder there.
So it's usually enough to use the following batch from within the buttercup folder when I want to keep my configuration folder also local,
Curiously enough it even worked ONCE, but after that buttercup always uses the original appdata folder. Is there another way to set the data folder like buttercup.exe --config=%cd%\datafolder ?