From: Mark Oteiza <mvoteiza@udel.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Should we just start dumping cl-lib?
Date: Fri, 2 Oct 2015 10:22:40 -0400 [thread overview]
Message-ID: <20151002142240.GA9755@holos> (raw)
In-Reply-To: <83pp0x5p7q.fsf@gnu.org>
On 02/10/15 at 05:18pm, Eli Zaretskii wrote:
> > Date: Fri, 2 Oct 2015 10:14:52 -0400
> > From: Mark Oteiza <mvoteiza@udel.edu>
> > Cc: emacs-devel@gnu.org
> >
> > Regarding the breakage with winner.el, I don't understand why under some
> > circumstances nothing seems to break if cl- functions are used at
> > runtime in things with only `(eval-when-compile (require 'cl-lib))`. For
> > instance, git-grepping for 'cl-remove-if' I see package.el and
> > checkdoc.el don't require cl-lib at runtime.
>
> Are the cl-lib functions they use auto-loaded, perhaps?
Yes. However, it was an issue in winner.el--why not in these libraries?
next prev parent reply other threads:[~2015-10-02 14:22 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
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 [this message]
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=20151002142240.GA9755@holos \
--to=mvoteiza@udel.edu \
--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 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.