(require 'org-publish) causes downgrade in org-version

(require 'org-publish) causes downgrade in org-version

[psycho_punch]

[-- Attachment #1: Type: text/plain, Size: 904 bytes --]

I have posted this question on StackOverflow
<http://stackoverflow.com/questions/24111890/org-mode-require-org-publish-causes-downgrade-in-org-version>
but in case you don't want to visit the page, I've pasted the contents in
this email.

I have just upgraded org-mode to the latest available in ELPA. According to
the official documentation, the installation has to be done in fresh emacs
session where no org-related scripts/files have been loaded. The
installation is successful, and org-version reports that I have updated to
8.2.6 (from 7.9.3f). However, as soon as I put back my old org-related
scripts, and reload emacs, I'd get 7.9.3f when I run org-version. To track
what's causing it I retrace my steps by adding my org-related scripts one
by one. I found out that when I add back (require 'org-publish), the
version downgrades to the built-in one. I don't know why this is happening.

Thanks.

[-- Attachment #2: Type: text/html, Size: 1031 bytes --]

Re: (require 'org-publish) causes downgrade in org-version

[Achim Gratz]

psycho_punch writes:
> I have just upgraded org-mode to the latest available in ELPA.
> According to the official documentation, the installation has to be
> done in fresh emacs session where no org-related scripts/files have
> been loaded. The installation is successful, and org-version reports
> that I have updated to 8.2.6 (from 7.9.3f). However, as soon as I put
> back my old org-related scripts, and reload emacs, I'd get 7.9.3f when
> I run org-version. To track what's causing it I retrace my steps by
> adding my org-related scripts one by one. I found out that when I add
> back (require 'org-publish), the version downgrades to the built-in
> one. I don't know why this is happening.

You need to replace this with (require 'ox-publish).  As to why this is
happening, you're sending Emacs down the wrong rabbit hole to search for
Org and the autoload stuff will do the rest.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves

Re: (require 'org-publish) causes downgrade in org-version

[rdgoite]

[-- Attachment #1: Type: text/plain, Size: 1323 bytes --]

I've tried replacing it with 'ox-publish but it can't be found. Does it
need to be installed separately?

---
sent through my mobile
On Jun 9, 2014 1:43 PM, "Achim Gratz" <Stromeko@nexgo.de> wrote:

> psycho_punch writes:
> > I have just upgraded org-mode to the latest available in ELPA.
> > According to the official documentation, the installation has to be
> > done in fresh emacs session where no org-related scripts/files have
> > been loaded. The installation is successful, and org-version reports
> > that I have updated to 8.2.6 (from 7.9.3f). However, as soon as I put
> > back my old org-related scripts, and reload emacs, I'd get 7.9.3f when
> > I run org-version. To track what's causing it I retrace my steps by
> > adding my org-related scripts one by one. I found out that when I add
> > back (require 'org-publish), the version downgrades to the built-in
> > one. I don't know why this is happening.
>
> You need to replace this with (require 'ox-publish).  As to why this is
> happening, you're sending Emacs down the wrong rabbit hole to search for
> Org and the autoload stuff will do the rest.
>
>
> Regards,
> Achim.
> --
> +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
>
> Wavetables for the Terratec KOMPLEXER:
> http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
>
>
>

[-- Attachment #2: Type: text/html, Size: 1830 bytes --]

Re: (require 'org-publish) causes downgrade in org-version

[psycho_punch]

[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]

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.


On Mon, Jun 9, 2014 at 1:42 PM, Achim Gratz <Stromeko@nexgo.de> wrote:

> psycho_punch writes:
> > I have just upgraded org-mode to the latest available in ELPA.
> > According to the official documentation, the installation has to be
> > done in fresh emacs session where no org-related scripts/files have
> > been loaded. The installation is successful, and org-version reports
> > that I have updated to 8.2.6 (from 7.9.3f). However, as soon as I put
> > back my old org-related scripts, and reload emacs, I'd get 7.9.3f when
> > I run org-version. To track what's causing it I retrace my steps by
> > adding my org-related scripts one by one. I found out that when I add
> > back (require 'org-publish), the version downgrades to the built-in
> > one. I don't know why this is happening.
>
> You need to replace this with (require 'ox-publish).  As to why this is
> happening, you're sending Emacs down the wrong rabbit hole to search for
> Org and the autoload stuff will do the rest.
>
>
> Regards,
> Achim.
> --
> +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
>
> Wavetables for the Terratec KOMPLEXER:
> http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
>
>
>

[-- Attachment #2: Type: text/html, Size: 2059 bytes --]

Re: (require 'org-publish) causes downgrade in org-version

[Achim Gratz]

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

Re: (require 'org-publish) causes downgrade in org-version

[psycho_punch]

[-- 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 --]

Re: (require 'org-publish) causes downgrade in org-version

[Alexis]

psycho_punch writes:

> 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...

They get loaded when (package-initialize) is called in one's
initialisation file(s).


Alexis.

Re: (require 'org-publish) causes downgrade in org-version

[psycho_punch]

[-- Attachment #1: Type: text/plain, Size: 683 bytes --]

So I need to explicitly call (package-initialize) in init.el, probably one
of the, if not the, first line?


On Mon, Jun 9, 2014 at 7:59 PM, Alexis <flexibeast@gmail.com> wrote:

>
> psycho_punch writes:
>
> > 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...
>
> They get loaded when (package-initialize) is called in one's
> initialisation file(s).
>
>
> Alexis.
>
>

[-- Attachment #2: Type: text/html, Size: 1190 bytes --]

Re: (require 'org-publish) causes downgrade in org-version

[Eric Abrahamsen]

psycho_punch <psychopunchme@gmail.com> writes:

> So I need to explicitly call (package-initialize) in init.el,
> probably one of the, if not the, first line?

If I recall correctly, the recommended thing is to put all of your
package-specific customizations either in the customize interface (in
which case they'll get applied correctly) or behind either a mode hook,
or an eval-after-load. Also see package-enable-at-startup, in the info
node (emacs) Package Installation

E

>
> On Mon, Jun 9, 2014 at 7:59 PM, Alexis <flexibeast@gmail.com> wrote:
>
>    
>     psycho_punch writes:
>    
>     > 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...
>    
>     They get loaded when (package-initialize) is called in one's
>     initialisation file(s).
>    
>    
>     Alexis.
>    

Re: (require 'org-publish) causes downgrade in org-version

[Jorge A. Alfaro-Murillo]

psycho_punch <psychopunchme@gmail.com> writes:

> So I need to explicitly call (package-initialize) in init.el, probably
> one of the, if not the, first line?

Yes, I had a similar issue with different versions from ELPA, and
applying (package-initialize) early (first line in my .emacs) fixed.

Re: (require 'org-publish) causes downgrade in org-version

[psycho_punch]

[-- Attachment #1: Type: text/plain, Size: 465 bytes --]

Yup. That works, too.

Thanks for all the help, everyone.


On Mon, Jun 9, 2014 at 9:42 PM, Jorge A. Alfaro-Murillo <
jorge.a.alfaro@gmail.com> wrote:

> psycho_punch <psychopunchme@gmail.com> writes:
>
> > So I need to explicitly call (package-initialize) in init.el, probably
> > one of the, if not the, first line?
>
> Yes, I had a similar issue with different versions from ELPA, and
> applying (package-initialize) early (first line in my .emacs) fixed.
>
>
>

[-- Attachment #2: Type: text/html, Size: 884 bytes --]