all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: Eli Zaretskii <eliz@gnu.org>
Cc: nicolas@petton.fr, juri@linkov.net, emacs-devel@gnu.org
Subject: Re: Making seq.el an Elpa core package?
Date: Mon, 11 Mar 2019 22:54:42 +0000	[thread overview]
Message-ID: <87o96hnhsd.fsf@russet.org.uk> (raw)
In-Reply-To: <831s3e7uel.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 10 Mar 2019 15:04:18 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: phillip.lord@russet.org.uk (Phillip Lord)
>> Date: Sun, 10 Mar 2019 11:48:50 +0000
>> Cc: Emacs Devel <emacs-devel@gnu.org>, Juri Linkov <juri@linkov.net>
>> 
>> I think that there is a lot to be said for explicit dependencies between
>> packages and minimizing the number of things that are pre-loaded. Most
>> packages load so quickly these days that the user rarely notices; or
>> wouldn't if we removed the "loading" messages.
>
> The principle always was that we preload packages which will be loaded
> by any session at startup or very soon afterwards anyway.  I don't
> think it matters how long do they load, because loading just once will
> always be faster.


Okay. I can see this for packages like "simple", perhaps "nadvice". I
struggle a bit with "language/sinhala", "uniquify" or even "isearch".

Phil



  reply	other threads:[~2019-03-11 22:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04 12:18 Making seq.el an Elpa core package? Nicolas Petton
2019-03-04 20:51 ` Juri Linkov
2019-03-04 22:42   ` Nicolas Petton
2019-03-10 11:48     ` Phillip Lord
2019-03-10 13:04       ` Eli Zaretskii
2019-03-11 22:54         ` Phillip Lord [this message]
2019-03-12  2:29           ` Stefan Monnier
2019-03-12 16:48 ` Stefan Monnier
2019-03-13  8:43   ` Nicolas Petton

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=87o96hnhsd.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --cc=nicolas@petton.fr \
    /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.