From: Ted Wiles <thewiles@wharton.upenn.edu>
To: ian@manor-farm.org
Cc: emacs-orgmode@gnu.org
Subject: Re: working on cloud
Date: Thu, 9 Jan 2014 10:03:10 -0500 [thread overview]
Message-ID: <87eh4hdwpd.fsf@dorewiles.com> (raw)
In-Reply-To: <52CE6262.8010405@wilkesley.net>
I used to use dropbox, but then I just went all-in, got some server
space from linode, and now I just SSH into a running emacs daemon. The
really cool thing is that I can also SSH in with my Droid 3 phone
(physical keyboard droids are the only ones I've found with the
requisite ctrl and meta keys).
Now, I never have to worry about versioning or maintaining multiple
.emacs, and org-mode is available wherever there is cell service
(grocery store, bus, etc.).
-----Original Message-----
From: Ian Barton
To: emacs-orgmode@gnu.org
Date: Thu 09 Jan 2014 03:48:34 AM EST
On 09/01/14 08:36, David Belohrad wrote:
> 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:
>
I have had problems with Dropbox generating "Conflicting files". I think
this is because some of my computers are only intermittently connected
to Dropbox. Sorting this out can be very time consuming, especially if
it happens inside a .git directory.
>
I have now gone down the git route for emacs init files and all my .org
files. I keep a separate branch for each computer and do a git pull and
git merge when I move to a different computer. This does have some
disadvantages - you need to remember to commit and push your changes on
each computer. However, sorting out mistakes is generally much easier.
>
Regarding your .emacs you can use elisp to distinguish various bits of
your configuration on an OS and computer name basis. Have a look at
http://sigquit.wordpress.com/2008/09/28/single-dot-emacs-file/ for a
good guide.
>
Ian.
next prev parent reply other threads:[~2014-01-09 15:03 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
2014-01-09 8:48 ` Ian Barton
2014-01-09 15:03 ` Ted Wiles [this message]
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=87eh4hdwpd.fsf@dorewiles.com \
--to=thewiles@wharton.upenn.edu \
--cc=emacs-orgmode@gnu.org \
--cc=ian@manor-farm.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).