emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Autoload `org-assert-version' and remove org-loaddefs.el
Date: Tue, 4 Apr 2023 19:08:18 +0700	[thread overview]
Message-ID: <u0h3vj$6hi$1@ciao.gmane.io> (raw)
In-Reply-To: <87zg7qjktr.fsf@localhost>

[-- Attachment #1: Type: text/plain, Size: 2692 bytes --]

On 02/04/2023 23:44, Ihor Radchenko wrote:
> 1. The old problem with mixed installation that manifests itself for
>     some users
> 2. The new problem with org-assert-version, which appears to be even
>     more frequent, despite trying preventing (1).

I leave decision up to you. My opinion that both cases are weird. With 
`org-assert-version' users become aware that Org is broken rather 
quickly, without it they have a time bomb that gives impression of bugs 
in Org. From my point of view the real issue is that in both cases error 
messages are not instructive. The downside of current implementation of 
`org-assert-version' is that Org does not work at all.

The above is related to *mixed compilation*, attempt to compile when 
some files from old version is loaded. The result is that some files are 
compiled with old macro definitions, some files are not compiled at all.

A different issue is *mixed load* when Org might be properly compiled, 
but at first some files from old version are loaded prior to adding the 
directory containing new version to load path.

I am not familiar with straight.el.

Ihor will you consider the issue as reproduced if I compile emacs from 
some tag in git repository on Debian or Ubuntu, not with provided binary 
packages? There are some funtoo LXC images, I never use it, so I have no 
idea how much time it will take to create build environment enough to 
build Emacs and how close it to Gentoo.

Do you consider the following as similar to package install issue for 
Emacs < 29? See the attachment

cd update-issue/
emacs -Q -l load-old-compile-new.el
emacs -Q -l load-new.el

==> old/upissue.el <==

(require 'upissue-macro)
(defun upissue-example (x) x)
(provide 'upissue)

==> old/upissue-macro.el <==

(defun upissue-macro-example (x) x)
(provide 'upissue-macro)

==> new/upissue.el <==

(require 'upissue-macro)
(defun upissue-example (x) x)
(provide 'upissue)

==> new/upissue-macro.el <==

(defmacro upissue-macro-check ()
   (message "upissue-macro-check called"))
(defun upissue-macro-example (x) x)
(provide 'upissue-macro)

==> compile-new.el <==
;; Compile new version
(add-to-list 'load-path (expand-file-name "new"))
(byte-recompile-directory "new" 0 :force)

==> load-new.el <==
;; Load new version
(setq debug-on-error t)
(add-to-list 'load-path (expand-file-name "new"))
(require 'upissue)

==> load-old-compile-new.el <==
;; Load old version
(add-to-list 'load-path (expand-file-name "old"))
(byte-recompile-directory "old" 0 :force)
(kill-buffer "*Compile-Log*")
(require 'upissue)
;; Compile new version
(add-to-list 'load-path (expand-file-name "new"))
(byte-recompile-directory "new" 0 :force)

[-- Attachment #2: update-issue.tar.gz --]
[-- Type: application/gzip, Size: 543 bytes --]

  reply	other threads:[~2023-04-04 12:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-01  7:26 [PATCH] Autoload `org-assert-version' and remove org-loaddefs.el Bastien
2022-12-02  3:38 ` Kyle Meyer
2022-12-02  7:44   ` Bastien
2022-12-03  4:18     ` Kyle Meyer
2022-12-06  3:54       ` David Masterson
2022-12-06  5:44         ` tomas
2022-12-06  7:13           ` David Masterson
2022-12-07 11:43     ` Ihor Radchenko
2022-12-07 14:08       ` Max Nikulin
2023-03-29 13:38     ` Ihor Radchenko
2023-03-29 16:04       ` Max Nikulin
2023-03-29 16:52         ` Ihor Radchenko
2023-04-01 14:44           ` Max Nikulin
2023-04-02  8:35             ` Ihor Radchenko
2023-04-02 15:59               ` Max Nikulin
2023-04-02 16:44                 ` Ihor Radchenko
2023-04-04 12:08                   ` Max Nikulin [this message]
2023-04-04 13:29                     ` Ihor Radchenko
2023-04-05 11:41                       ` Max Nikulin
2023-04-08 16:47           ` Max Nikulin
2023-04-09  8:29             ` Ihor Radchenko
2023-04-10  6:13               ` Max Nikulin
2023-04-10 16:58                 ` Ihor Radchenko
2023-06-04 10:58                   ` Max Nikulin
2022-12-06  3:00   ` David Masterson

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='u0h3vj$6hi$1@ciao.gmane.io' \
    --to=manikulin@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).