emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: psycho_punch <psychopunchme@gmail.com>
To: emacs-orgmode@gnu.org
Subject: (require 'org-publish) causes downgrade in org-version
Date: Mon, 9 Jun 2014 07:56:29 +0800	[thread overview]
Message-ID: <CADWK+fczA=vm2xMt6Zc0bp23QxaSRngsMwecMQD=5dXsNdeQBQ@mail.gmail.com> (raw)

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

next             reply	other threads:[~2014-06-08 23:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-08 23:56 psycho_punch [this message]
2014-06-09  5:42 ` (require 'org-publish) causes downgrade in org-version 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
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+fczA=vm2xMt6Zc0bp23QxaSRngsMwecMQD=5dXsNdeQBQ@mail.gmail.com' \
    --to=psychopunchme@gmail.com \
    --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

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