From: David Masterson <dsmasterson@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: emacs-devel@gnu.org, John Wiegley <johnw@gnu.org>,
Justin Talbott <justin@waymondo.com>
Subject: use-package: Problem with built-in packages?
Date: Wed, 07 Dec 2022 22:08:57 -0800 [thread overview]
Message-ID: <SJ0PR03MB5455B916953BB0E13ADA7EBFA21D9@SJ0PR03MB5455.namprd03.prod.outlook.com> (raw)
In-Reply-To: <CADwFkmm-Pd482ooJ64WOPEX=bOq0BfWnVTGrys_U1tCiEsC1qw@mail.gmail.com> (Stefan Kangas's message of "Wed, 7 Dec 2022 16:19:46 -0800")
I've run into a problem with installing Org-9.6 with use-package that I
wonder if it might be a general problem with use-package.
Org-9.6 (IIRC) introduced org-assert-version that everything in Org now
depends on. I load many (all?) packages with use-package. The problem
I get (once I fixed up my ":after" setting in the other packages) is a
:catch when loading Org-9.6:
Error (use-package): org/:catch: Invalid function: org-assert-version
The problem is that I'm using a pre-built Emacs v2.7 which has Org-9.3
built-in. Testing says that Org is not loaded before the use-package
for Org. Therefore, something is happening in the use-package for Org
that is causing Org to be loaded before the load-path is properly set
(thus, causing the :catch).
Does this make sense? Hmm, I guess I should try adding Org-9.6to the
load-path before the use-package for Org. If I'm right, everything
should start working.
What do you think?
--
David Masterson
next prev parent reply other threads:[~2022-12-08 6:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 23:36 use-package: Should we merge bind-chords.el / use-package-chords.el? Stefan Kangas
2022-12-08 0:19 ` Stefan Kangas
2022-12-08 0:58 ` John Wiegley
2022-12-08 6:08 ` David Masterson [this message]
2022-12-08 16:37 ` use-package: Problem with built-in packages? Stefan Kangas
2022-12-08 18:25 ` 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SJ0PR03MB5455B916953BB0E13ADA7EBFA21D9@SJ0PR03MB5455.namprd03.prod.outlook.com \
--to=dsmasterson@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=johnw@gnu.org \
--cc=justin@waymondo.com \
--cc=stefankangas@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.