emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Reload uncompiled needed
Date: Fri, 18 Feb 2022 09:44:10 +1100	[thread overview]
Message-ID: <87zgmpw1dh.fsf@gmail.com> (raw)
In-Reply-To: <87y229cxm0.fsf@hornfels.zedat.fu-berlin.de>

"Loris Bennett" <loris.bennett@fu-berlin.de> writes:

> Hi,
> I have managed to install 9.5 but I now get 
>   org-agenda-get-day-entries: Invalid function: (date date)
> when I try to generate my agenda.  If I reload Org uncompiled, the error
> disappears.
> In *Messages* it seems like the very same version has been reloaded:
>   Org mode version 9.5.2 (9.5.2-gfbff08 @ /home/loris/.emacs.d.default/elpa/org-9.5.2/)
>   Successfully reloaded Org
>   Org mode version 9.5.2 (9.5.2-gfbff08 @ /home/loris/.emacs.d.default/elpa/org-9.5.2/)
> If I try to byte recompile the directory, everything seems
> up-to-date:
>   Checking /home/loris/.emacs.d.default/elpa/org-9.5.2/... [125 times]
>   Checking /home/loris/.emacs.d.default/elpa/org-9.5.2/doc...
>   Checking /home/loris/.emacs.d.default/elpa/org-9.5.2/etc...
>   Checking /home/loris/.emacs.d.default/elpa/org-9.5.2/etc/csl...
>   Checking /home/loris/.emacs.d.default/elpa/org-9.5.2/etc/styles...
>   Done (Total of 0 files compiled, 124 skipped)
> The el and elc files seem to have the same date:
>   $ ll ~/.emacs.d.default/elpa/org-9.5.2/org.el*
>   -rw-r--r-- 1 loris users 834072 Feb  9 16:45 /home/loris/.emacs.d.default/elpa/org-9.5.2/org.el
>   -rw-r--r-- 1 loris users 719363 Feb  9 16:45 /home/loris/.emacs.d.default/elpa/org-9.5.2/org.elc
> I can't pretend to understand the contents of org.elc, but it does
> contain the following
>   (provide \\='org-xyz)\n\nFor export specific modules, see also
>   `org-export-backends'." :group org :set org-set-modules
>   :package-version (Org . "9.5")
> The version which comes with Emacs 27 on Debian seems to be 9.3:
>   $ zgrep '^;; Version' /usr/share/emacs/27.1/lisp/org/org.el.gz
>   ;; Version: 9.3
> I presume I could just delete all the elc-files, but I would like to
> know what is going on.  Can anyone see what is happening?

How did you upgrade? (package.el, straight.el, manual git clone etc)?

Did you make sure no org functionality was already loaded into Emacs
before you performed the upgrade?

If you try to upgrade org using a apckage manager, such as package.el,
and you already have some org functionality loaded at the time of the
upgrade, you can get a broken 'mixed' installation. This will often
create the type of errors you are experiencing.

The solution is to uninstall the upgraded version, start a new Emacs
session which has no org functionality loaded (may be necessary to
comment out any org related configuration in your init file to prevent
org being loaded at startup), upgrade org to current version and then
restore your init setup code. Depending on what configuration code you
ahve in your init file and how it is structured, sometimes it is
sufficient to just ensure you do the upgrade immediately after starting
a new Emacs session. Where people run into problems is when they upgrade
org in an Emacs session which has been running for some time (and which
likely has some org functionality already loaded). 

  reply	other threads:[~2022-02-17 22:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17 15:37 Loris Bennett
2022-02-17 22:44 ` Tim Cross [this message]
2022-02-18  7:47   ` Joost

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:

  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=87zgmpw1dh.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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