[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Should we just start dumping cl-lib?
From: |
Eli Zaretskii |
Subject: |
Re: Should we just start dumping cl-lib? |
Date: |
Fri, 02 Oct 2015 11:07:33 +0300 |
> Date: Fri, 02 Oct 2015 10:19:12 +0300
> From: Eli Zaretskii <address@hidden>
> Cc: address@hidden
>
> 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.
OTOH, visiting a C file or a file in Outline mode loads cl-lib, so
perhaps it's indeed time to preload it.
- Should we just start dumping cl-lib?, Daniel Colascione, 2015/10/08
- Re: Should we just start dumping cl-lib?, John Wiegley, 2015/10/08
- Re: Should we just start dumping cl-lib?, Daniel Colascione, 2015/10/08
- Re: Should we just start dumping cl-lib?, Eli Zaretskii, 2015/10/08
- Re: Should we just start dumping cl-lib?, Artur Malabarba, 2015/10/08
- Re: Should we just start dumping cl-lib?, Andreas Schwab, 2015/10/08
- Re: Should we just start dumping cl-lib?, Artur Malabarba, 2015/10/08
- Re: Should we just start dumping cl-lib?, Rasmus, 2015/10/08
- Re: Should we just start dumping cl-lib?,
Eli Zaretskii <=
- Re: Should we just start dumping cl-lib?, Oleh Krehel, 2015/10/08
Re: Should we just start dumping cl-lib?, Mark Oteiza, 2015/10/08