Eric Schulte <schulte.e...@gmail.com> wrote: > I attempted to apply your suggestions to my init.el resulting in the > following > > > (add-hook 'after-init-hook > `(lambda () > (require 'org) > (setq features (remove 'org-macs features)) > (add-to-list 'load-path "~/.emacs.d/src/org-mode/lisp/") > (load-file "~/.emacs.d/src/org-mode/lisp/org.el") > (org-reload))) >
> > It yields these errors on startup > > *Messages* > Loading /home/eschulte/.emacs.d/src/org-mode/lisp/org.el (source)... > Package assoc is obsolete! > Loading /home/eschulte/.emacs.d/elpa/org-20121231/org-loaddefs.el > (source)...done > Problems while trying to load feature `org-jsinfo' > eval-buffer: Symbol's function definition is void: > org-define-obsolete-function-alias > > It looks like removing items from `features' is dangerous. > I don't think so: I got the org-define-obsolete-function-alias error when trying to org-reload this morning (resolved by manually loading org-compat.el before doing the org-reload again): it's another instance of the same problem. You also don't seem to have an org-loaddefs.el in the git clone, so it loads the one it finds in the ELPA dir. You should ``make autoloads''. > If this problem is specific to my situation I'm happy to ignore it until > I can update my elpa version of Org-mode to a newer one. Alternately I > could just remove my ELPA install of Org-mode, as it was only installed > to answer questions on the mailing list, and I don't think side-by-side > ELPA and source Org-modes are necessarily something that needs to be > supported. > I'm pretty sure it is. It would probably be better to have two separate installations and have different init files for each. The side-by-side installations is an invitation to a franken-install. Nick
