From: Robert Horn <rjhorn@alum.mit.edu>
To: Bastien <bzg@altern.org>, Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Babel related bug in elpa version 20121231
Date: Sat, 05 Jan 2013 11:40:49 -0500 [thread overview]
Message-ID: <m3623boa5q.fsf@quad.robs.office> (raw)
In-Reply-To: <87wqvrc2hu.fsf@bzg.ath.cx>
Bastien <bzg@altern.org> writes:
>
> I also wish Emacs can read an ~/.emacs.org init file.
>
That is what the starterkit for emacs 24 is attempting to do. It's got
a ~/init.el that is just
#+begin_src emacs-lisp
(setq starter-kit-dir
(file-name-directory (or load-file-name (buffer-file-name))))
;; load up the starter kit
(org-babel-load-file (expand-file-name "starter-kit.org"
starter-kit-dir))
#+end_src
All of my problems seem to arise from the bad interactions between
starting with the built-in package version of org that is used by the
org-babel-load-file, and then transitioning part way through its
execution of the starter-kit.org to the elpa updated version of org.
The result is much like a mixed version install of org. Strange things
go wrong.
I like having the nicely formatted and documented setup that I get with
an export to html of the org files that contain the startup scripts. My
intended mode of operation is to have a customized set of starterkit.org
files that can apply to everyone, with each user also having a
~/.emacs.d/<user>.org and a ~/.emacs.d/<machine>.org to provide further
user customizations, including per machine variations for users who need
different setups on different machines.
R Horn
rjhorn@alum.mit.edu
next prev parent reply other threads:[~2013-01-05 16:40 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 15:03 org version under Windows 7 Giovanni Ridolfi
2012-07-11 16:46 ` Achim Gratz
2012-07-11 17:43 ` [PATCH] " Achim Gratz
2012-07-11 20:21 ` Bastien
2012-07-11 21:15 ` Achim Gratz
2012-07-12 6:31 ` Bastien
2012-07-12 8:30 ` Giovanni Ridolfi
2012-07-12 13:24 ` Achim Gratz
2012-07-24 15:23 ` Bastien
2012-07-25 7:52 ` Giovanni Ridolfi
2012-07-26 12:50 ` Bastien
2012-07-26 18:49 ` Achim Gratz
2012-07-31 16:36 ` Bastien
2013-01-02 22:22 ` Babel related bug in elpa version 20121231 Robert Horn
2013-01-04 2:16 ` Robert Horn
2013-01-04 15:23 ` Bastien
2013-01-04 21:27 ` Achim Gratz
2013-01-05 0:10 ` Robert Horn
2013-01-05 7:07 ` Achim Gratz
2013-01-05 11:07 ` Bastien
2013-01-05 11:45 ` Achim Gratz
2013-01-05 12:33 ` Bastien
2013-01-05 13:40 ` Achim Gratz
2013-01-05 14:00 ` Bastien
2013-01-05 16:40 ` Robert Horn [this message]
2013-01-05 16:55 ` Achim Gratz
2013-01-05 18:51 ` Eric Schulte
2013-01-05 19:07 ` Achim Gratz
2013-01-05 19:28 ` Eric Schulte
2013-01-05 20:39 ` Achim Gratz
2013-01-05 23:29 ` Eric Schulte
[not found] ` <CAGoVJLFRky2wOZUkyAVTp3E9eXnsYoetAckWKJs1MKyqQHUCFA@mail.gmail.com>
2013-01-05 20:55 ` Fwd: " Stelian Iancu
2013-01-05 21:16 ` Eric Schulte
2013-01-05 21:10 ` Robert Horn
2013-01-05 22:14 ` Tom Davey
2013-01-05 23:30 ` Eric Schulte
2013-01-06 20:21 ` Stelian Iancu
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=m3623boa5q.fsf@quad.robs.office \
--to=rjhorn@alum.mit.edu \
--cc=Stromeko@nexgo.de \
--cc=bzg@altern.org \
--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).