Just to drop in my two cents... I've used unison before for working with
syncing to a USB stick. It was okay, especially when I only had a couple of
machines to think about.
I've recently been thinking about something like DropBox or Ubuntu One, but
I keep thinking that I would rather have my information in my own control. I
have some hosted servers that have enough space to handle what I would need
from Zim (I only have about 1 meg of current data -- but this is likely to
go up to up to several gig fairly quickly with some of the projects I have
Personally, I prefer a solution that implements something like sshfs or
rsync+ssh. I've also considered the idea of using subversion or git over
ssh...but I don't know that I have a space online that would allow me to set
up the necessary version repositories.
However, while a cron job would handle most of the problem extremely well,
it wouldn't be ideal for all situations: such as laptop(s) / netbook, where
the sync really needs to happen more "on demand". That's one problem...
The other problem I've seen with more recent copies of Zim is the way the
config file is handled now. Keeping it in ~/.config/zim has just added a
layer of complication to keeping everything in sync. (This has "freaked" me
out a few times when I've synced my files and opened Zim, only to find that
a new notebook doesn't show up...because I'd neglected to sync the config
files) It would be nice to allow the user to specify where the configuration
directory is stored (say via a command line option)... Why would this help?
becuase then it would be possible to keep the config info with the notebook
directories...then it's just one directory to sync, instead of trying to
remember to sync two locations.
Okay - enough of that. Just my two cents.
On Fri, Nov 20, 2009 at 6:28 PM, Pedro <pedro...@gmail.com> wrote:
> Ok everybody, we should get back on topic.
> There are many possibilities, i myself use a bazaar repository over SSH and
> am quite happy with it.
> But that is not what i intended to discuss. For example, in my case, i have
> to manually commit and push the changes to the remote branch, i'm kind of ok
> with that but i don't think that is very intuitive for a less tech savy
> person. Also, it could be cool to set it up once and forget it. first thing
> we need is working implementations, then we can worry about whatever
> services are out there suporting those technologies and how accessible they
> So, at the very least a page would be saved once the user either navigates
> to another page or quits zim. I believe the saving process happens more
> often than that. Jaap, can you jump in the discussion and drop a quick
> briefing of the basics on zim data storage?
> On Fri, Nov 20, 2009 at 8:00 PM, Svenn Are Bjerkem <
> svenn.bjer...@googlemail.com> wrote:
>> 2009/11/20 Dotan Cohen <dotanco...@gmail.com>:
>> > Svenn, can you share some commands or scripts? I have played with
>> > unison in the distant past and discounted it, but if you have a
>> > working solution I'd love to see it.
>> Unfortunately, I am using Unison the hard way, by the GUI. This is
>> mainly the reason why syncing happens too seldom in my case. The FAQ
>> recomend to use a star topology, with one common server.
>> The GUI version is fast and fires up my favourite merge tool when
>> needed, but that doesn't help when I forget to use it.
>> Mailing list:
>> Post to : firstname.lastname@example.org
>> Unsubscribe :
>> More help : https://help.launchpad.net/ListHelp
> Mailing list:
> Post to : email@example.com
> Unsubscribe :
> More help : https://help.launchpad.net/ListHelp
Faster moments spent spread tales of change within the sound...
Mailing list: https://launchpad.net/~zim-wiki
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~zim-wiki
More help : https://help.launchpad.net/ListHelp