From: Kyle Meyer <email@example.com>
To: Bastien <firstname.lastname@example.org>
Subject: Re: [PATCH] Autoload `org-assert-version' and remove org-loaddefs.el
Date: Thu, 01 Dec 2022 22:38:03 -0500 [thread overview]
Message-ID: <email@example.com> (raw)
> Some users reported an (invalid-function org-assert-version) error
> when installing Org from ELPA:
> This patch autoloads `org-assert-version'.
I don't understand the rationale behind this. Every spot that calls
org-assert-version is preceded by a line that requires org-macs, so
isn't this error likely due to a mixed installation/load-path issue
where the wrong/older org-macs is taking precedence?
> It also removes the ;; generated-autoload-file: "org-loaddefs.el"
> footer in all files and let Make create org-autoloads.el instead.
I'm worried with how this will play with the Org bundled with Emacs.
The autoloads that are now written to lisp/org/org-loaddefs.el will
instead pollute the top-level lisp/loaddefs.el.
When I tested this out in the Emacs repo, running `make` shows many
WARNING: No org-autoloads.el file could be found from where org.el
You need to run "make" or "make autoloads" from Org lisp directory
during the build. And loading/using Org shows the same.
> Before the patch, installing from ELPA creates both org-loaddefs.el
> and org-autoloads.el, which is confusing.
Hmm, isn't this in line with the lisp/org-loaddefs.el and
lisp/loaddefs.el split that happens for the Emacs repo?
A similar split is used other packages in the Emacs repo as well:
$ find lisp | grep '\-loaddefs.el' | head
$ find lisp | grep -c '\-loaddefs.el'
$ find lisp | grep -c '\-autoloads.el'
And with the port of Emacs's 2682ea1b3 (Org commit 19c3969e7,
2022-10-04), there's also one spot that uses ;;;###org-autoload, which
tells loaddefs-gen.el to direct the autoload to org-loaddefs.el.
> Unless anyone objects, I'll install this patch in the bugfix branch
> tomorrow and release 9.6.1.
I think as is the patch would cause issues, and more generally I'm not
convinced we should be moving away from having an org-loaddefs.el file.
I'm also concerned about this sort of tree-wide change in a patch
release that will be synced to the emacs-29 branch.
Thanks for posting this for discussion, and please let me know if I'm
mistaken about the interaction with the Emacs repo.
next prev parent reply other threads:[~2022-12-02 3:39 UTC|newest]
Thread overview: 10+ 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 [this message]
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
2022-12-06 3:00 ` David Masterson
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 \
* 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).