all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: use-package :after ??
Date: Fri, 12 May 2023 08:31:39 +0200	[thread overview]
Message-ID: <87lehuxdpw.fsf@dataswamp.org> (raw)
In-Reply-To: 83lehu3wkl.fsf@gnu.org

Eli Zaretskii wrote:

>> For instance, what happens if A should be after B, but you
>> never define B with use-package?
>
> Isn't it clear? If B is never loaded, A will _never_ be
> loaded in that case. It doesn't matter whether B is loaded
> via use-package or by some other means. How is this NOT
> clear from the description?
>
>> Or B is demand loaded later?
>
> Later than what? A will _always_ be loaded as the last step
> in loading B, whenever the latter happens.
>
>> Or make the rule explicit in infodoc that :after does what
>> it does regardless of demand/defer.
>
> So is the difficulty because of :defer and/or :demand?
> If so, please ask questions that involve those. Because so
> far you were asking about :after alone, and there I see
> nothing unclear.

Why should this be done manually at all?

For example, a source file should just say, I need X, Y and
Z since I use stuff from those.

What order they are loaded shouldn't matter since they are
all needed. Also, whatever stuff they themselves need is up to
them to solve - with the same simple method, preferably.

-- 
underground experts united
https://dataswamp.org/~incal




  reply	other threads:[~2023-05-12  6:31 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08  0:05 use-package :after ?? David Masterson
2023-05-08  2:44 ` 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 [this message]
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=87lehuxdpw.fsf@dataswamp.org \
    --to=incal@dataswamp.org \
    --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.