From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Schmitt Subject: Re: Using Eric Schulte's starter kit with org mode from source Date: Wed, 24 Apr 2013 11:34:01 +0200 Message-ID: References: <87y5ca67ra.fsf@gmail.com> <878v49mgew.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:55827) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UUw5Z-0008E8-0O for emacs-orgmode@gnu.org; Wed, 24 Apr 2013 05:34:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UUw5U-0000ZG-9W for emacs-orgmode@gnu.org; Wed, 24 Apr 2013 05:34:08 -0400 Received: from mail2-relais-roc.national.inria.fr ([192.134.164.83]:63355) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UUw5U-0000Z0-3J for emacs-orgmode@gnu.org; Wed, 24 Apr 2013 05:34:04 -0400 In-reply-to: <878v49mgew.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Eric Schulte Cc: emacs-orgmode Hi Eric, Eric Schulte writes: > I can think of some possibilities, > > 1. Your load-path either isn't pointing to the newest Org-mode, or you > are somehow also loading an older version of Org-mode. Although I > believe I just helped you setup your load path, so lets assume this > isn't the case. > > 2. Do you explicitly require whichever ox-* new exporter you want to > use? > > 3. Maybe you should run make in the Org-mode directory, to ensure all > autoload files etc... are in place. I'm sure there is a way around > having to do this every time, but it may help in this instance. > > Sorry I can't be of more help. If the solution you find appears to be a > general one, please let me know if it should be folded into the starter > kit. I haven't been able to find why this happens, but I have an idea for a workaround: I'll put my export settings in another file (for instance "export.org"). Then I'll have a special init file ("export-init.el") that sets up the org path and loads that file. I have two questions about how to make it work nice in the starter kit context. In export-init.el, should I do a (load-file "export.el") or is it better to do a (org-babel-load-file "export.org")? In my main configuration file, should I do a #+include "export.org", or is it better to do a "org-babel-load-file"? Thanks, Alan