emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Greg Minshall <minshall@umich.edu>
To: Tim Cross <theophilusx@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Fwd: errors when using org-agenda
Date: Sat, 23 Oct 2021 13:26:12 +0300	[thread overview]
Message-ID: <1366768.1634984772@apollo2.minshall.org> (raw)
In-Reply-To: <m25ytopjg9.fsf@blind-drunk.fritz.box>

Tim, et al.,

> These types of errors are frequently caused by a 'mixed' installation
> of org versions. This will happen if you upgrade org when org is
> already loaded in the instance of emacs used to perform the upgrade.

a question: is there any way that we can, as org starts up, detect
either the actuality, or possibility, of a mixed installation?
maybe something like
----
(assert (eq 1
            (length
             (seq-filter
              (lambda (d) (file-exists-p (concat d "/" "org.el")))
              load-path))))
----
or some such?  (well, maybe fail in a more user-friendly way... :)

cheers, Greg


  reply	other threads:[~2021-10-23 10:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22 20:35 errors when using org-agenda William McCoy
2021-10-23  0:46 ` Fwd: " William McCoy
2021-10-23  1:57   ` Tim Cross
2021-10-23 10:26     ` Greg Minshall [this message]
2021-10-23 11:34       ` Tim Cross
2021-10-23 18:07         ` Greg Minshall
2021-10-23 18:21           ` Tim Cross
2021-10-24  0:45             ` Thomas S. Dye
2021-10-24  5:05         ` Greg Minshall
2021-10-24  6:44           ` Tim Cross
2021-10-24 10:55             ` Greg Minshall
2021-10-24  5:12         ` [PATCH] " Ihor Radchenko
2021-10-24  6:59           ` Tim Cross
2021-10-24  8:16       ` Max Nikulin
2021-10-24  8:34         ` Ihor Radchenko
2021-10-27 16:46           ` Max Nikulin
2022-09-11  9:22             ` Ihor Radchenko
2021-10-23 14:49     ` William McCoy

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=1366768.1634984772@apollo2.minshall.org \
    --to=minshall@umich.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=theophilusx@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).