From: torys.anderson@gmail.com (Tory S. Anderson)
To: emacs-orgmode@gnu.org
Subject: Re: Favorite way of syncing?
Date: Fri, 11 Sep 2015 09:25:19 -0600 [thread overview]
Message-ID: <87d1xpyo4g.fsf@torysa-worldsendless.byu.edu> (raw)
In-Reply-To: <87a8strnm3.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Fri, 11 Sep 2015 23:18:12 +0800")
At the moment I'm using a self-hosted OwnCloud to do syncing; it's
super easy (takes care of itself), but sometimes conflicts are a
problem (particularly when I forget to save my buffers before
leaving work); if you notice it, though, it provides a conflict
version (and has automatic versioning a la Dropbox).
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo) writes:
>
>> Tobias Frischholz writes:
>>
>>> I was wondering what is your favorite way of syncing your org
>>> files
>>> and everything.
>> [...]
>>> I’ve also read about org-sync and magit (git is an option for
>>> me).
>>> And now I’m starting the get confused.
>>
>> magit is just the emacs mode for git, if you don't have it and
>> use git
>> you should really install it. But it does not sync anything you
>> still
>> have to M-x magit <enter> F F and M-x magit <enter> P P, for
>> pull and
>> push.
>>
>> I have several computers and synchronize my org files with
>> git. I
>> think it is the best option because I do not have to worry
>> about the
>> sync not working (for example when I do not have a connection)
>> and
>> conflicts in the files.
>
> I do this, too. I don't think Magit helps much, in fact I'd be
> better
> off writing functions for `emacs-startup-hook' and
> `kill-emacs-hook'
> that do my pushes and pulls for me.
>
> But for now, I just try to remember to commit and push before I
> leave a
> machine.
>
> This way, you also really learn to appreciate using "git fetch"
> and "git
> status", rather than doing a blind "git pull".
>
> Eric
>
>
>
--
Tory S. Anderson
Computational Cognitive Narratologist
http://toryanderson.com
next prev parent reply other threads:[~2015-09-11 15:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 13:59 Favorite way of syncing? Tobias Frischholz
2015-09-11 14:27 ` Alan Schmitt
2015-09-11 14:47 ` Jorge A. Alfaro-Murillo
2015-09-11 15:18 ` Eric Abrahamsen
2015-09-11 15:25 ` Tory S. Anderson [this message]
2015-09-11 15:48 ` Joon Ro
[not found] ` <34AA198A-5C08-4FDD-8D12-5241E44A0B9D@friolz.com>
2015-09-12 1:15 ` Eric Abrahamsen
2015-09-11 15:13 ` Paul Rudin
2015-09-11 15:18 ` Eric S Fraga
2015-09-11 16:42 ` Ramon Diaz-Uriarte
2015-09-11 20:47 ` Eric S Fraga
2015-09-13 7:07 ` Paul Rudin
2015-09-13 19:18 ` Ramon Diaz-Uriarte
2015-09-11 22:05 ` Myles English
2015-09-11 22:51 ` Kyle Meyer
2015-09-12 1:24 ` Eric Abrahamsen
2015-09-14 9:34 ` Myles English
2015-09-15 2:07 ` Eric Abrahamsen
2015-09-12 5:18 ` Erik Hetzner
2015-09-12 13:31 ` Rasmus
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=87d1xpyo4g.fsf@torysa-worldsendless.byu.edu \
--to=torys.anderson@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).