From: Grant Rettke <gcr@wisdomandwonder.com>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>, Peter Davis <pfd@pfdstudio.com>
Subject: Re: Keeping up to date
Date: Tue, 29 Apr 2014 18:12:35 -0500 [thread overview]
Message-ID: <CAAjq1md5QRoFLZj-kQzntR6jr+D7d-ZWgoaVGofsD2Z3pKVHFw@mail.gmail.com> (raw)
In-Reply-To: <CA+M2ft86aOmNcTXqKo-_yvM9w5Act0QxZ5tVDa8nL7tQTv29EQ@mail.gmail.com>
I use Cask https://github.com/cask/cask for 5 machines and it works
quite well if you like that style.
Grant Rettke | AAAS, ACM, ASA, FSF, IEEE, SIAM, Sigma Xi
grettke@acm.org | http://www.wisdomandwonder.com/
“Wisdom begins in wonder.” --Socrates
((λ (x) (x x)) (λ (x) (x x)))
“Life has become immeasurably better since I have been forced to stop
taking it seriously.” --Thompson
On Tue, Apr 29, 2014 at 3:34 PM, John Hendy <jw.hendy@gmail.com> wrote:
> On Tue, Apr 29, 2014 at 1:27 PM, Peter Davis <pfd@pfdstudio.com> wrote:
>> Thanks, John (and Greg) for your replies.
>>
>> At some point, I'm going to have to bite the bullet and put all my emacs stuff in a Dropbox folder, so all my Macs will be in sync all the time. Apart from org-mode versions, I
>> have inconsistencies in init files, etc. that cause me headaches. John, I'm inclined to agree that getting all my init stuff sync'ed is more important, but I think part of that is
>> having all packages in one place so they're in sync as well.
>
> I wondered about that. Technically, it seemed you only mentioned
> Emacs/Org, which I wasn't sure if that encompassed Emacs (the binary
> application), other Emacs .el files, and Org, or if you just meant
> keeping your Emacs binary version up to date (and Emacs doesn't rev
> /that/ often).
>
> If you meant the former ("Emacs" meant your stash of various .el
> files), then I agree that an be a headache. I'll often try some .el
> program du jour, maybe keep it, maybe not, and just have them littered
> about it ~/.elisp/site-lisp. Then I potentially have to add a line to
> add that to my load path if it's a more involved program with it's on
> dir vs. being a singular .el file. So, yes, that's a bit of a headache
> as well and I think if you are doing a bunch with extra Emacs add-ons,
> it would be worth syncing.
>
> I'm thinking I fiddle with some .el or another perhaps 2-4 times a
> year, so again, it's not really impacting me.
>
>
> John
>
>>
>> Thanks!
>> -pd
>>
>>
>> --
>> ----
>> Peter Davis
>> The Tech Curmudgeon
>> www.techcurmudgeon.com
>>
>
next prev parent reply other threads:[~2014-04-29 23:12 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
2014-04-29 18:27 ` Peter Davis
2014-04-29 20:34 ` John Hendy
2014-04-29 23:12 ` Grant Rettke [this message]
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:
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=CAAjq1md5QRoFLZj-kQzntR6jr+D7d-ZWgoaVGofsD2Z3pKVHFw@mail.gmail.com \
--to=gcr@wisdomandwonder.com \
--cc=emacs-orgmode@gnu.org \
--cc=jw.hendy@gmail.com \
--cc=pfd@pfdstudio.com \
/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).