all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
	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 13:38:27 +0100	[thread overview]
Message-ID: <CAAdUY-+SJUxFNOMBD1i4KXfu4qyi9gSumEX3jdr_vjQuM89yWQ@mail.gmail.com> (raw)
In-Reply-To: <874mi9a2bl.fsf@igel.home>

2015-10-02 13:21 GMT+01:00 Andreas Schwab <schwab@linux-m68k.org>:
> They should require it only during compiling.

That's only viable if they only use macros. Many of them use functions
from cl-lib so they need a proper require.

Below is a list of all files which grep for ^(require 'cl-lib), which
means they require it at runtime. If any of these are expected to be
loaded at the start of every session, then we should either fix that
require or preload cl-lib.
The ones tat catch my attention are vc.el and help-mode.el.

man.el:92
emacs-lisp/cl.el:30
emacs-lisp/cl-extra.el:40
emacs-lisp/edebug.el:56
emacs-lisp/cl-seq.el:44
emacs-lisp/ert.el:60
emacs-lisp/generator.el:79
emacs-lisp/cl-macs.el:46
emacs-lisp/eieio-core.el:34
dom.el:27
calendar/parse-time.el:37
calendar/todo-mode.el:57
doc-view.el:139
frameset.el:41
wid-edit.el:58
edmacro.el:66
url/url-http.el:28
midnight.el:39
shadowfile.el:78
vc/vc.el:710
vc/ediff-init.el:27
eshell/em-ls.el:29
eshell/em-term.el:34
image-dired.el:159
profiler.el:29
desktop.el:138
progmodes/sql.el:229
progmodes/hideif.el:107
progmodes/ebrowse.el:36
progmodes/xref.el:53
progmodes/gdb-mi.el:94
progmodes/python.el:262
thumbs.el:60
help-mode.el:33
help-fns.el:35
net/gnutls.el:38
net/rcirc.el:46
net/nsm.el:27
net/sasl-scram-rfc.el:40
woman.el:417



  reply	other threads:[~2015-10-02 12:38 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
2015-10-02 12:21         ` Andreas Schwab
2015-10-02 12:38           ` Artur Malabarba [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAAdUY-+SJUxFNOMBD1i4KXfu4qyi9gSumEX3jdr_vjQuM89yWQ@mail.gmail.com \
    --to=bruce.connor.am@gmail.com \
    --cc=dancol@dancol.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=schwab@linux-m68k.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.