From: psycho_punch <psychopunchme@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: (require 'org-publish) causes downgrade in org-version
Date: Mon, 9 Jun 2014 19:36:04 +0800 [thread overview]
Message-ID: <CADWK+fdXUVjXBX6qUHsqrsEFWkr8RoXK8XoOwhq5L+GrJH21uQ@mail.gmail.com> (raw)
In-Reply-To: <87bnu2wdgm.fsf@Rainer.invalid>
[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]
I've defined my initialization script in ~/.emacs.d/init.el; I'm not sure
if it matters. So since 'ox-publish doesn't get loaded until after
initialization, I defined:
(add-hook 'after-init-hook (lambda() (load-file
"/path/to/org-publish-project.el")))
I'm wondering when do the packages installed via package-install get
loaded...
On Mon, Jun 9, 2014 at 7:04 PM, Achim Gratz <Stromeko@nexgo.de> wrote:
> psycho_punch writes:
> > Ok, so apparently, ox-publish doesn't get loaded after init in my
> > setup; I'm not sure why. What I have done so far is to run the publish
> > script after init using the after-init-hook. However, I feel like this
> > shouldn't be how it's done.
>
> It's hard to tell, but you're likely trying to configure Org before
> package-initialize has run.
>
>
> Regards,
> Achim.
> --
> +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
>
> Factory and User Sound Singles for Waldorf Q+, Q and microQ:
> http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
>
>
>
[-- Attachment #2: Type: text/html, Size: 1651 bytes --]
next prev parent reply other threads:[~2014-06-09 11:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-08 23:56 (require 'org-publish) causes downgrade in org-version psycho_punch
2014-06-09 5:42 ` Achim Gratz
2014-06-09 6:18 ` rdgoite
2014-06-09 8:17 ` psycho_punch
2014-06-09 11:04 ` Achim Gratz
2014-06-09 11:36 ` psycho_punch [this message]
2014-06-09 11:59 ` Alexis
2014-06-09 12:16 ` psycho_punch
2014-06-09 12:43 ` Eric Abrahamsen
2014-06-09 13:42 ` Jorge A. Alfaro-Murillo
2014-06-09 13:53 ` psycho_punch
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=CADWK+fdXUVjXBX6qUHsqrsEFWkr8RoXK8XoOwhq5L+GrJH21uQ@mail.gmail.com \
--to=psychopunchme@gmail.com \
--cc=Stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.org \
--cc=psychopunch.me@gmail.com \
/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).