From: "Jan Böcker" <jan.boecker@jboecker.de>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-orgmode@gnu.org
Subject: Re: Plans for synching with Emacs dev sources?
Date: Tue, 13 Apr 2010 23:57:37 +0200 [thread overview]
Message-ID: <4BC4E8D1.6010704@jboecker.de> (raw)
In-Reply-To: <87iq7v9kj9.fsf@telefonica.net>
On 13.04.2010 22:15, Óscar Fuentes wrote:
> Currently I'm using 6.33x, which is the version that comes with Emacs
> dev source code. I'll like to use a more recent version of org-mode, and
> so I ask if there are plans for upgrading Emacs' org-mode sources with
> the current release. If not, I'll use org-mode git sources, although
> this would complicate a bit the deployment across several machines.
AFAIK that happens whenever a new major version of emacs is released,
which is very infrequently.
Even if the next version of emacs would be just around the corner, you'd
just find yourself in the situation of using a very outdated version
again within a few weeks.
However, deployment across several machines can be easy with git. My
~/.emacs.d is a git repository which contains all my emacs configuration
and elisp library files. I have added org-mode as a submodule here, so
after running git pull && git submodule update on another machine,
everything is in sync again.
I use the org-babel approach to emacs configuration. In my startup.org,
the first toplevel subtree contains code that finds out what machine it
is running on by looking at the hostname and sets the variable
jb/system. I have one toplevel subtree for common configuration and two
for settings specific to one of my two machines.
- Jan
next prev parent reply other threads:[~2010-04-13 21:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 20:15 Plans for synching with Emacs dev sources? Óscar Fuentes
2010-04-13 21:57 ` Jan Böcker [this message]
2010-04-13 22:37 ` Eric Schulte
2010-04-14 6:27 ` Carsten Dominik
2010-04-14 17:23 ` Eric Schulte
2010-04-14 7:32 ` Ian Barton
2010-04-15 10:16 ` Carsten Dominik
2010-04-15 12:29 ` Óscar Fuentes
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=4BC4E8D1.6010704@jboecker.de \
--to=jan.boecker@jboecker.de \
--cc=emacs-orgmode@gnu.org \
--cc=ofv@wanadoo.es \
/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).