unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Ihor Radchenko <yantar92@posteo.net>,
	 kyle@kyleam.com, emacs-devel@gnu.org
Subject: Re: master 5a125fb5a97 1/2: Update to Org 9.7.3
Date: Tue, 11 Jun 2024 09:16:17 -0400	[thread overview]
Message-ID: <jwv34pjmyak.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <8634pj7jni.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 11 Jun 2024 15:23:29 +0300")

>> Note that org-num.el where `org-num-skip-tags' is defined does have
>> (require 'cl-lib).
>>
>> IMHO, there is some problem either with loaddefs generation or with the
>> fact that loaddefs file is compiled at all.

Code that's in an ;;;###autoload cookie is copied verbatim to the
loaddefs file, so it cannot assume that all the earlier code in the file
(e.g. the `(require 'cl)` at the beginning of the file) has been executed.

> No, the problem is that this variable uses cl-lib stuff for safep
> functions.  IMO, this is not a good idea, and the above situation is
> precisely the evidence for that.

In theory, `org-loaddefs.el` could be arranged to require `cl-lib` (we
don't want that in `loaddefs.el` but it'd be OK for `org-loaddefs.el`).
In practice, the generation of `org-loaddefs.el` currently doesn't offer
an easy way to insert some ad-hoc code like `(require 'cl-lib)` at
the beginning.  We should fix that because it's a relatively common need
(especially since the relative ordering of elements from different
files is not guaranteed).

> Stefan, WDYT about this issue?

While you're at it, please don't autoload the vars:
autoload only the safety declaration.


        Stefan




  parent reply	other threads:[~2024-06-11 13:16 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <171796793548.23337.12512115872160390161@vcs2.savannah.gnu.org>
     [not found] ` <20240609211858.A2C31C1F9FB@vcs2.savannah.gnu.org>
2024-06-10  0:40   ` master 5a125fb5a97 1/2: Update to Org 9.7.3 Po Lu
2024-06-10  1:14     ` Kyle Meyer
2024-06-10  3:45       ` Po Lu
2024-06-10  3:58         ` Po Lu
2024-06-12 13:08         ` Ihor Radchenko
2024-06-12 13:13           ` Eli Zaretskii
2024-06-12 13:23             ` Ihor Radchenko
2024-06-12 13:30               ` Eli Zaretskii
2024-06-14 13:18                 ` Ihor Radchenko
2024-06-10 11:13       ` Eli Zaretskii
2024-06-11 10:05         ` Ihor Radchenko
2024-06-11 12:23           ` Eli Zaretskii
2024-06-11 13:10             ` Robert Pluim
2024-06-14  9:49               ` Ihor Radchenko
2024-06-14 11:39                 ` Eli Zaretskii
2024-06-14 12:02                   ` Robert Pluim
2024-06-11 13:16             ` Stefan Monnier [this message]
2024-06-12 13:49               ` Ihor Radchenko
2024-06-12 14:41                 ` Stefan Monnier
2024-06-13 13:00             ` Ihor Radchenko
2024-06-13 13:43               ` Eli Zaretskii
2024-06-13 14:34                 ` Stefan Monnier
2024-06-14 12:39                 ` Ihor Radchenko
2024-06-13 13:32             ` Ihor Radchenko
2024-06-13 13:54               ` Eli Zaretskii
2024-06-15 11:20                 ` Ihor Radchenko
2024-06-15 12:46                   ` Eli Zaretskii
2024-06-15 12:55                     ` Syncing Org bugfix releases with emacs-30 branch (was: master 5a125fb5a97 1/2: Update to Org 9.7.3) Ihor Radchenko
2024-06-15 13:02                       ` Eli Zaretskii
2024-06-16 11:09                         ` Ihor Radchenko
2024-06-15 16:58                     ` master 5a125fb5a97 1/2: Update to Org 9.7.3 Kyle Meyer
2024-06-11 11:03   ` Stefan Kangas
2024-06-12  3:45     ` Kyle Meyer
2024-06-12  8:52       ` Eli Zaretskii
2024-06-12 12:58         ` Ihor Radchenko
2024-06-12 13:02           ` Eli Zaretskii
2024-06-12 13:21             ` Ihor Radchenko
2024-06-12 13:29               ` Eli Zaretskii
2024-06-12 14:14                 ` Stefan Kangas
2024-06-13 16:12                   ` Ihor Radchenko
2024-06-13 16:48                     ` Eli Zaretskii
2024-06-12 14:46             ` Stefan Monnier
2024-06-12 16:50               ` Eli Zaretskii
2024-06-13 15:44                 ` Ihor Radchenko
2024-06-13 15:55                   ` Eli Zaretskii

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwv34pjmyak.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=kyle@kyleam.com \
    --cc=yantar92@posteo.net \
    /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.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).