Thorsten Jolitz <tjol...@googlemail.com> wrote:
> Eric Schulte <schulte.e...@gmail.com> writes:
>
> > Thorsten Jolitz <tjol...@googlemail.com> writes:
> >
> >> Eric Schulte <schulte.e...@gmail.com> writes:
> >>
> >>> If you are using the starter-kit, then Org-mode is required as the first
> >>> step of your Emacs initialization. This is necessary so that the
> >>> `org-babel-load-file' function can be used to load your customization
> >>> from .org files. In this case the best (only) way to ensure that the
> >>> most recent version of Org-mode is loaded is to add the path to your
> >>> Org-mode install to the emacs command line with something like the
> >>> following.
> >>>
> >>> emacs --eval "(add-to-list 'load-path \"~/src/org-mode/lisp/\")"
> >>>
> >>> This may be simplified with a command line alias like the following.
> >>>
> >>> alias emacs="emacs --eval '(add-to-list (quote load-path)
> >>> \"~/src/org-mode/lisp/\")'"
> >>>
> >>> When I find time I plan to add this to the starter-kit documentation.
> >>
> >> That would be a good idea, I remember having exactly that problem in the
> >> past using the starter-kit, but I worked it out somehow.
> >>
> >> At the moment I seem to have a more basic problem, since starting with
> >> emacs -Q the system knows about the org directory:
> >>
> >> M-x locate-library RET org.el:
> >> Library is file /usr/share/emacs/24.2/lisp/org/lisp/org.el
> >>
> >
> > Org-mode is built into Emacs, so there will be an Org-mode in the load
> > path from the moment Emacs starts. This is not a problem in and of
> > itself.
>
> I do have my bad experiences with mixed installations, so the first
> thing I do when I install or update Emacs is to trash the Org-mode that
> comes with Emacs and replace it with a symlink to the git version.
>
> > The important thing is to put the path to the Org-mode you want to use
> > on the front of the load path (either with the command line flag above
> > or with an `add-to-list' in your config) *before* the first time
> > Org-mode is required with a (require 'org). That should be sufficient.
>
> Now I started Emacs with:
>
> $ emacs --eval "(add-to-list 'load-path \"~/gitclone/org-mode/lisp/\")"
>
> and the load-path looks like this:
>
> load-path
> ("~/gitclone/org-mode/lisp/" "/home/tj/.emacs.d/elpa/auctex-11.86/"...)
>
> but nevertheless, opening an .org file gives me:
> File mode specification error:
> (void-function org-define-obsolete-function-alias)
>
There is no such function in current org (either defined or used). The
remaining instance was deleted in this commit:
,----
| commit 655ba9f9391e9dafb72a97cea1e327692ac83855
| Author: Nicolas Goaziou <n.goaz...@gmail.com>
| Date: Sun Jan 13 20:58:21 2013 +0100
|
| Remove left-over `org-define-obsolete-function-alias'
`----
which you probably don't have. Update org would be my advice.
Nick
> So this seems to be a different problem, maybe related to this recent
> message from Paul Sexton:
>
> From: Paul Sexton <psexton...@gmail.com>
> Subject: Re: Fixes for org-capture-templates-contexts
> Newsgroups: gmane.emacs.orgmode
> To: emacs-orgmode@gnu.org
> Date: Mon, 14 Jan 2013 22:21:20 +0000 (UTC) (13 hours, 8 minutes ago)
>
> (...)
> Also, very important. I updated to master in order to make the patch and found
> the current orgmode does not compile or even load. This is because
> ob-eval.el uses 'declare-function' which is undefined (it is defined in
> org-macs.el but ob-eval.el does not require that file).
> (...)
>
> --
> cheers,
> Thorsten
>
>
