From: David Belohrad <david@belohrad.ch>
To: Paul Rudin <paul@rudin.co.uk>, emacs-orgmode@gnu.org
Subject: Re: working on cloud
Date: Thu, 09 Jan 2014 09:36:40 +0100 [thread overview]
Message-ID: <uaxd2k1zh47.fsf@beesknees.cern.ch> (raw)
In-Reply-To: <877ga9d11a.fsf@rudin.co.uk>
I was using before Dropbox for all sort of syncing, especially my org
mode files, which change quite often. Dropbox is generally very fine (as
well e.g. for sharing screenshots between windows and linux
machines). At certain moment I started to have two issues with this:
1) privacy: you're basically giving your data to somebody else. In case
of emacs init there is no danger. In case of your org data, which
might contain sensitive information you want to encrypt it, what
complicates matter when switching between two win/lin machines
2) deadlocks on files. When working in agenda, quite often happened to
me, that files started to exist in multiple versions. When I took my
laptop somewhere without wifi signal and edited files, dropbox
created local copy of this. When in between I have changed that file
on some other computer with wifi, this file was correctly synced with
dropbox. At the time, when my laptop appeared again on wifi, it tried
to sync the file, but as it was in-between edited, it resulted quite
often in having two files containing almost the same things, which i
had to manually merge. what a pain. this was the main reason I went
away from dropbox.
Unfortunately there is no easy solution for this. I tried to use AFS
as well, with the same results. The only 'reasonable' way I found for
this was to use local git copies and do merging, which most of the
time passes completely automatically without a need for intervention
(as far as you don't use mobileorg, which adds unique IDs for items
--> this must be disabled for proper git functionality)
As I said, imho Dropbox is fine for emacs init files (not containing
passwords :). For general stuff it seems to me less obvious.
.d.
Paul Rudin <paul@rudin.co.uk> writes:
> David Belohrad <david@belohrad.ch> writes:
>
>> I use for all emacs files git with server repository. Then on each
>> computer I'm using emacs with, I just clone that repository. The
>> positive side-effect of this is, that when you need to modify sources
>> for a particular computer, you just create new local branch. Then all
>> 'common' init file tweaks can be done in master branch and it is very
>> easy to merge them into local one if needed....
>
> Yes, I have done that sort of thing in the past, but I find the need to
> check stuff in and push/pull and merge unnecessary overheads for this
> kind of thing. Just leaving the file on Dropbox (or whatever) means that
> things are synced automagically when edited which, nearly all the time,
> is what I want. Dropbox keeps a limited revision history for the free
> version (which I use) or you can pay and get an unlimited revision
> history. Of course that's not as useful as using git in terms of merging
> and so on, but it does provide some protection against erroneous
> changes.
>
>
> For added fun keep the git (or whatever) repository on a Dropbox folder
> - this means that you get the automatic updating for things in progress,
> but you can also use the proper version control features too.
next prev parent reply other threads:[~2014-01-09 8:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 18:59 working on cloud Renato
2014-01-08 19:28 ` Nick Dokos
2014-01-08 19:32 ` Sam Flint
2014-01-08 21:28 ` Joseph Vidal-Rosset
2014-01-08 23:35 ` John Kitchin
[not found] ` <CAF83ECCdCt8NZK-h5O1t8_M5PytxcvJf71R6csqaBHYLCwM5=A@mail.gmail.com>
2014-01-11 15:38 ` John Kitchin
2014-01-09 7:19 ` Paul Rudin
2014-01-09 8:00 ` David Belohrad
2014-01-09 8:14 ` Paul Rudin
2014-01-09 8:36 ` David Belohrad [this message]
2014-01-09 8:48 ` Ian Barton
2014-01-09 15:03 ` Ted Wiles
2014-01-09 15:28 ` Brett Viren
-- strict thread matches above, loose matches on Subject: below --
2014-01-13 11:52 Renato Pontefice
2014-01-13 11:54 ` Bastien
2014-01-14 11:45 ` Renato Pontefice
2014-01-14 12:24 ` Nick Dokos
2014-01-14 12:58 ` Alexander Baier
2014-01-14 7:20 ` Paul Rudin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uaxd2k1zh47.fsf@beesknees.cern.ch \
--to=david@belohrad.ch \
--cc=emacs-orgmode@gnu.org \
--cc=paul@rudin.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).