From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: (require 'org-publish) causes downgrade in org-version
Date: Mon, 09 Jun 2014 07:42:40 +0200 [thread overview]
Message-ID: <87oay2wsdr.fsf@Rainer.invalid> (raw)
In-Reply-To: CADWK+fczA=vm2xMt6Zc0bp23QxaSRngsMwecMQD=5dXsNdeQBQ@mail.gmail.com
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
next prev parent reply other threads:[~2014-06-09 5:43 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 [this message]
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
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=87oay2wsdr.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).