From: David Masterson <dsmasterson@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: use-package :after ??
Date: Sun, 07 May 2023 17:05:57 -0700 [thread overview]
Message-ID: <SJ0PR03MB5455104C024684D2C723DE79A2719@SJ0PR03MB5455.namprd03.prod.outlook.com> (raw)
Didn't see this post, so ...
This might be a documentation problem...
I'm not sure I understand ":after" (and a few other related things) in
use-package. The info docs talk about it ensuring that the current
package is loaded after the other listed packages, but it's not quite
explicit (to me) about what that means. I interpret it in two possible
ways:
1. If any of the listed packages are not loaded currently, then the
current package will not be loaded. Period.
2. #1 + "magic" will be done to ensure that, once the listed packages
are loaded, the current package will be (auto?) loaded.
If #1 is correct, I do not know how the current package will ever be
loaded if ":after" fails. If #2 is correct, I do not know what the
"magic" could be to safely do this.
My goal is to organwize my .emacs loading of 25+ packages to only load if
needed. That means (almost) all packages are deferred at startup and
will load itself and subpackages (minor modes, etc.) when I try to call
the package. This is what I hoped :after was for.
Can someone advise on the proper use of ":after" and how to get
appropriate subpackages to also load when the main package is loaded.
For instance:
(use-package org-ac :after org)
(use-package org)
--
David Masterson
next reply other threads:[~2023-05-08 0:05 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 0:05 David Masterson [this message]
2023-05-08 2:44 ` use-package :after ?? Ruijie Yu via Users list for the GNU Emacs text editor
2023-05-08 4:05 ` David Masterson
2023-05-08 4:25 ` Ruijie Yu via Users list for the GNU Emacs text editor
2023-05-08 5:20 ` David Masterson
2023-05-08 12:19 ` Eli Zaretskii
2023-05-10 23:56 ` David Masterson
2023-05-11 3:24 ` David Masterson
2023-05-11 6:14 ` Eli Zaretskii
2023-05-11 21:24 ` David Masterson
2023-05-12 1:18 ` Ruijie Yu via Users list for the GNU Emacs text editor
2023-05-12 6:33 ` Eli Zaretskii
2023-05-12 6:38 ` Emanuel Berg
2023-05-12 5:59 ` Eli Zaretskii
2023-05-12 6:54 ` David Masterson
2023-05-12 7:22 ` Eli Zaretskii
2023-05-15 6:03 ` David Masterson
2023-05-15 11:36 ` Eli Zaretskii
2023-05-15 22:19 ` David Masterson
2023-05-16 16:16 ` Eli Zaretskii
[not found] ` <87pm72m8rc.fsf@penguin>
2023-05-15 6:16 ` David Masterson
2023-05-15 11:42 ` Eli Zaretskii
2023-05-15 22:27 ` David Masterson
2023-05-16 16:19 ` Eli Zaretskii
2023-05-16 20:44 ` David Masterson
2023-05-17 1:40 ` David Masterson
2023-05-17 11:42 ` Eli Zaretskii
2023-05-17 20:30 ` David Masterson
2023-05-18 10:36 ` Eli Zaretskii
2023-05-18 12:41 ` Lynn Winebarger
2023-05-19 2:40 ` David Masterson
2023-05-19 3:03 ` David Masterson
2023-05-11 5:54 ` Eli Zaretskii
2023-05-11 22:04 ` David Masterson
2023-05-12 6:14 ` Eli Zaretskii
2023-05-12 6:31 ` Emanuel Berg
2023-05-12 6:56 ` 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=SJ0PR03MB5455104C024684D2C723DE79A2719@SJ0PR03MB5455.namprd03.prod.outlook.com \
--to=dsmasterson@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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.