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: [PATCH] Autoload `org-assert-version' and remove org-loaddefs.el
Date: Tue, 04 Apr 2023 13:29:36 +0000	[thread overview]
Message-ID: <87mt3nai7z.fsf@localhost> (raw)
In-Reply-To: <u0h3vj$6hi$1@ciao.gmane.io>

Max Nikulin <manikulin@gmail.com> writes:

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

I guess we might try to run a poll. My view on this bug is rather skewed
as I saw it too many times. The true number of Org users affected may
actually vary.

> 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?

Sure. Anything Emacs devs can act on. If you can prove that the problem
is in Emacs source code, we can report it in
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=59882 and let Emacs devs
fix things.

Currently, it looks like Debian modifies certain aspects of Emacs
loading. In such scenario, we cannot expect things to be fixed on Emacs

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

This looks like

But Emacs >26 + package-install specifically arranges unloading the
older version of the library. It should not suffer from this (in

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:[~2023-04-04 13:28 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
2023-04-04 13:29                     ` Ihor Radchenko [this message]
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=87mt3nai7z.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=manikulin@gmail.com \


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