emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Peter Davis <pfd@pfdstudio.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Keeping up to date
Date: Tue, 29 Apr 2014 11:45:01 -0500	[thread overview]
Message-ID: <CA+M2ft_SvPviaK0PB=0Gx8k2oSc_9as_u1U6_Tzi6f_RchUojA@mail.gmail.com> (raw)
In-Reply-To: <20140429161623.GA72660@pdavismbp15.iscinternal.com>

On Tue, Apr 29, 2014 at 11:16 AM, Peter Davis <pfd@pfdstudio.com> wrote:
> A while ago, I switched from ELPA to Git as my Org-mode source. However, I now have three Macs I'm trying to keep in sync, and doing Git updates is definitely more labor
> intensive. Any suggestions for good ways to keep three machines all up-to-date with Emacs and Org?

If by Org, you mean the Orgmode files and not your .org files, I don't
find it difficult. Once anywhere from 1x/week to 1x/month, I simply
$ cd ~/.elisp/org.git
$ git pull
$ make clean && make

Then again, I don't do any local branches or development, so it might
be more difficult if you had files changed you'd need to merge, etc.
The above could probably even be put into a script. There's also
makeupN commands that I still have on my todo list to re-look into. I
think those even integrate the git pull/make steps, so you'd just need
to cd to your org.git repo and execute that.

> I suppose the best thing would be to put all my emacs stuff in a Dropbox folder and run from that, but I haven't managed to overcome the inertia to get that working.

The % of time that being on the bleeding edge of Org would have helped
me with some issue is minimal. There are great instances where I've
made a mailing list post and a change has been pushed to fix it nearly
immediately. But I tend to have initiated those anyway. Thus, I really
don't think most folks would notice a performance/feature benefit from
updating 1x/day and 1x/month (maybe even longer). Feel free to

Regarding updating Emacs, this again seems super infrequent. I'm
mostly using Arch Linux, so the updates come whenever the repo
changes. My Win7 work computer would be a lot more similar to keeping
a Mac up to date, and I only update Emacs (aka, delete the old folder,
download a new version) maybe once or twice a year.

Sorry if the above was nothing new to you. Primarily, I'm trying to
understand what you find very difficult or trying. Or is it just doing
the above three times on separate computers that's annoying? I
definitely get that, though I'd invest in sharing the same
configurations between the systems before trying to get org.git and
Emacs running off of dropbox. Changes to .emacs that would propagate
to other computers would seem (to me, at least) *much* more impactful
than keeping Org/Emacs synced.


> Org-mode is now my most heavily used emacs mode by far (though that may change if I ever get back to coding in a "real" programming language.)
> Thanks,
> -pd
> --
> ----
> Peter Davis
> The Tech Curmudgeon
> www.techcurmudgeon.com

  parent reply	other threads:[~2014-04-29 16:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-29 16:16 Keeping up to date Peter Davis
2014-04-29 16:44 ` Greg Troxel
2014-04-29 16:45 ` John Hendy [this message]
2014-04-29 18:27   ` Peter Davis
2014-04-29 20:34     ` John Hendy
2014-04-29 23:12       ` Grant Rettke
2014-04-30 17:51         ` "Clément B."

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:

  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='CA+M2ft_SvPviaK0PB=0Gx8k2oSc_9as_u1U6_Tzi6f_RchUojA@mail.gmail.com' \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=pfd@pfdstudio.com \


* 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


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).