unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: emacs-devel@gnu.org
Subject: Re: Should we just start dumping cl-lib?
Date: Fri, 02 Oct 2015 10:19:12 +0300	[thread overview]
Message-ID: <83r3ld7n67.fsf@gnu.org> (raw)
In-Reply-To: <560E1615.2020002@dancol.org>

> From: Daniel Colascione <dancol@dancol.org>
> Date: Thu, 1 Oct 2015 22:28:53 -0700
> 
> >> Commit d605a539d4863c7e7c66aaea6e538ae14c47f3d7 broke Emacs when winner was
> >> enabled without cl-lib being loaded. Nobody seems to have noticed until now,
> >> which suggests that either almost nobody uses winner, or almost everybody
> >> has cl-lib loaded anyway. Maybe it's time to just dump cl-lib with Emacs.
> > 
> > I use winner, but always have cl-lib loaded.
> 
> So does almost everyone else, apparently.

Only those who use winner, apparently.  This incident tells us nothing
about those who don't use winner, right?

> So let's save everyone some initialization CPU time and preload
> cl-lib.

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.



  reply	other threads:[~2015-10-02  7:19 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 [this message]
2015-10-02  8:07       ` Eli Zaretskii
2015-10-02  8:23       ` Artur Malabarba
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=83r3ld7n67.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dancol@dancol.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).