emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Using Eric Schulte's starter kit with org mode from source
Date: Wed, 24 Apr 2013 20:07:40 +0200	[thread overview]
Message-ID: <m2y5c7dcpf.fsf@polytechnique.org> (raw)
In-Reply-To: <87bo93keb2.fsf@gmail.com>

Eric Schulte writes:

>>
>> I've turned on the debugger, and there is something that I find a bit
>> strange. Here are the last few lines.
>>
>> ,----
>> |   load("/var/folders/68/fvntfrw92y50gkk_67rkhsfw0000gn/T/org-export-process77683E90" nil t)
>> |   command-line-1(("-l" "/Users/schmitta/.emacs.d/init.el" "-l" "/var/folders/68/fvntfrw92y50gkk_67rkhsfw0000gn/T/org-export-process77683E90"))
>> |   command-line()
>> |   normal-top-level()
>> `----
>>
>> Why is it loading the second file first? Shouldn't it load init.el
>> first? Is it because of the "after-init-hook"?
>
> Yes, the starter kit waits to load on the after-init-hook so that the
> Emacs package system will be fully loaded.  That is why the other file
> you load on the command line is loaded first.

Then asynchronous export can't work, as it needs ox in that file. I've
changed my init.el to loading org before the after-init-hook, and I go
further but then I have an error about the "koma-letter" being
unknown. It seems that to go this way I would need to load all of my
export settings before the after-init-hook.

So going the route of having a special init file for that seems even
more relevant now. So I'll ask again: if I want to put some
configuration in another .org file, it is better to #+include it in my
main org configuration file, or to org-babel-load-file it?

Thanks again for your help,

Alan

PS: I really don't understand how configuration options that are loaded
in the after-init-hook can be used during asynchronous export. Is it
working for you (with a more usual org install)?

  reply	other threads:[~2013-04-24 18:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-22 12:31 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
2013-04-24 17:31             ` Alan Schmitt
2013-04-24 17:51               ` Eric Schulte
2013-04-24 18:07                 ` Alan Schmitt [this message]
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
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=m2y5c7dcpf.fsf@polytechnique.org \
    --to=alan.schmitt@polytechnique.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@gmail.com \
    --subject='Re: Using Eric Schulte'\''s starter kit with org mode from source' \
    /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

Code repositories for project(s) associated with this 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).