From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Daniel Colascione <dancol@dancol.org>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Should we just start dumping cl-lib?
Date: Fri, 2 Oct 2015 09:23:48 +0100 [thread overview]
Message-ID: <CAAdUY-+pA_WBO_wVVN9PAi4q4RfNGqbbKvM+w64RFx2YMh1Bkg@mail.gmail.com> (raw)
In-Reply-To: <83r3ld7n67.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 626 bytes --]
> Up until now, the rules for pre-loading package X were that either
> (a) some preloaded package requires X, or (b) X will be auto-loaded at
> the beginning of every session by some very frequent operation, like
> visiting the first file or creating a window or a frame.
>
> Since winner is itself an optional package that not everyone uses
> (e.g., I don't), this case doesn't seem to qualify, IMO.
This might still be an instance of (b), given how many packages require
cl-lib. It would be useful if someone grepped together a list of all such
packages so we could figure how often it'll just be loaded at startup
anyway.
[-- Attachment #2: Type: text/html, Size: 722 bytes --]
next prev parent reply other threads:[~2015-10-02 8:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 4:52 Should we just start dumping cl-lib? Daniel Colascione
2015-10-02 5:12 ` John Wiegley
2015-10-02 5:28 ` Daniel Colascione
2015-10-02 7:19 ` Eli Zaretskii
2015-10-02 8:07 ` Eli Zaretskii
2015-10-02 8:23 ` Artur Malabarba [this message]
2015-10-02 12:21 ` Andreas Schwab
2015-10-02 12:38 ` Artur Malabarba
2015-10-02 14:27 ` Rasmus
2015-10-02 7:21 ` Oleh Krehel
2015-10-02 11:46 ` Mark Oteiza
2015-10-02 13:37 ` Tassilo Horn
2015-10-02 15:22 ` Artur Malabarba
2015-10-02 13:45 ` Eli Zaretskii
2015-10-02 14:14 ` Mark Oteiza
2015-10-02 14:18 ` Eli Zaretskii
2015-10-02 14:22 ` Mark Oteiza
2015-10-02 14:38 ` Eli Zaretskii
2015-10-02 16:07 ` John Wiegley
2015-10-03 0:19 ` Daniel Colascione
2015-10-03 7:22 ` Eli Zaretskii
2015-10-04 1:24 ` Daniel Colascione
2015-10-04 6:48 ` Eli Zaretskii
2015-10-02 15:13 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAdUY-+pA_WBO_wVVN9PAi4q4RfNGqbbKvM+w64RFx2YMh1Bkg@mail.gmail.com \
--to=bruce.connor.am@gmail.com \
--cc=dancol@dancol.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).