emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug? org-assert-version does not prevent mixed install
Date: Sun, 18 Dec 2022 14:26:33 +0000	[thread overview]
Message-ID: <87h6xs6b52.fsf@localhost> (raw)
In-Reply-To: <tnn6pl$18c$1@ciao.gmane.io>

Max Nikulin <manikulin@gmail.com> writes:

>> We might do something like
>> 
>> (eval-and-compile (org-assert-version))
>
> This will give obscure error during compiling since `org-assert-version' 
> is not defined.
>
> Unsure what will happen during load of the org.el file since org.elc is 
> not produced. Perhaps the same cryptic error, but I can not explain it.

Yes, but we will at least abort the compilation this way.

> My idea (unchecked)
>
> ;; Remove when support of Emacs-29 is dropped.
> (unless (fboundp 'org-assert-version)
>    (error "Org is compiled or loaded while older version loaded already. 
>   Please, ensure that no other org versions are loaded and recompile."))

I guess we can use the same error with what `org-assert-version' itself
throws:

(error "Org version mismatch.  Make sure that correct `load-path' is set early in init.el")

If you can, please check it. (AFAIU, you do have a setup where you can
reproduce the installation problem)

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2022-12-18 14:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-18  5:20 Bug? org-assert-version does not prevent mixed install Max Nikulin
2022-12-18 13:04 ` Ihor Radchenko
2022-12-18 14:06   ` Max Nikulin
2022-12-18 14:26     ` Ihor Radchenko [this message]
2022-12-27 16:32       ` Max Nikulin
2022-12-28  9:46         ` Ihor Radchenko
2023-01-04 11:27           ` Max Nikulin

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=87h6xs6b52.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=manikulin@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).