From: Eric Schulte <schulte.eric@gmail.com>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
Eric Schulte <schulte.eric@gmail.com>
Subject: Re: Using Eric Schulte's starter kit with org mode from source
Date: Wed, 24 Apr 2013 09:08:00 -0600 [thread overview]
Message-ID: <87a9ookkxn.fsf@gmail.com> (raw)
In-Reply-To: m261zcff1y.fsf@polytechnique.org
Alan Schmitt <alan.schmitt@polytechnique.org> writes:
> 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
I don't understand why you can't put this code into your normal
configuration file? If the error is thrown *before* your main
configuration file is loaded, then my guess is that something is wrong
with your Org-mode install. I'd read the worg pages on setting up a
local Org-mode install to make sure everything there checks out.
Hope this helps,
--
Eric Schulte
http://cs.unm.edu/~eschulte
next prev parent reply other threads:[~2013-04-24 15:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 12:31 Using Eric Schulte's starter kit with org mode from source Alan Schmitt
2013-04-22 12:59 ` Eric Schulte
2013-04-22 14:11 ` Alan Schmitt
2013-04-23 7:42 ` Alan Schmitt
2013-04-23 13:27 ` Eric Schulte
2013-04-24 9:34 ` Alan Schmitt
2013-04-24 15:08 ` Eric Schulte [this message]
2013-04-24 17:31 ` Alan Schmitt
2013-04-24 17:51 ` Eric Schulte
2013-04-24 18:07 ` Alan Schmitt
2013-04-24 18:25 ` Eric Schulte
2013-04-24 19:29 ` Thomas S. Dye
2013-04-25 7:27 ` Alan Schmitt
2013-04-25 15:29 ` Eric Schulte
2013-04-26 8:02 ` Alan Schmitt
-- strict thread matches above, loose matches on Subject: below --
2013-04-24 19:29 Alexander Poslavsky
2013-04-24 20:29 ` Eric Schulte
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=87a9ookkxn.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=alan.schmitt@polytechnique.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).