NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
--Mark Hahn, <hahn@neurocog.lrdc.pitt.edu>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
And here I thought… (Score:1)
… that this was called “putting your home directory in version control.”
But hey, reinventing version control in every app that needs to be configurable is a fine solution too. Don’t mind me, I’m just a cranky oldster, and now I have to go back to shooing kids off my lawn. :-)
Re: (Score:1)
Have you ever tried doing that across multiple different operating systems?
Re: (Score:1)
I have in fact carried my Vim configuration back and forth to Windows and MacOS X machines (whereas my native environment is Linux). I didn’t use version control at the time, but that wouldn’t make a fundamental difference in feasibility.
Re: (Score:1)
You didn't do it with version control... which was my entire point.
Of course you can move one file here and there.
When running multiple copies at the same time... (Score:2)
Changes made on one Padre install (for example, if you want your comments pink instead of grey) appear auto-magically in the other Padre installs next time you start them.
So, what happens if you change the color of your comments in one instance, while running another instance on another computer... Will the latter overwrite the new cloud preferences when you turn it off, while saving its own preferences? What if you changed a (different) preference there, too?
Re: (Score:1)
In the initial implementation, I would expect that it will be a simple naive "last to save wins". I don't want to do too many tricks.
So it will only fetch the config at startup time.
A second generation implementation will likely be needed to move that from that simplest possible version to something that uses real sync/merge logic.