From: Nicolas Petton <nicolas@petton.fr>
To: Mark Oteiza <mvoteiza@udel.edu>, emacs-devel@gnu.org
Subject: Re: Should we just start dumping cl-lib?
Date: Fri, 02 Oct 2015 17:13:36 +0200 [thread overview]
Message-ID: <87pp0xgv6n.fsf@petton.fr> (raw)
In-Reply-To: <87twq9ebmh.fsf@udel.edu>
[-- Attachment #1: Type: text/plain, Size: 648 bytes --]
Mark Oteiza <mvoteiza@udel.edu> writes:
> Daniel Colascione <dancol@dancol.org> writes:
>
>> 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.
>
> Bug#21549
>
> I'd be happy to have more useful functions in "core". (Can we have
> `filter` yet?)
It's not in "core", it's not preloaded, but seq.el provides useful
additional sequence-manipulation functions such as `seq-filter'.
Nico
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
prev parent reply other threads:[~2015-10-02 15:13 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
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 [this message]
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=87pp0xgv6n.fsf@petton.fr \
--to=nicolas@petton.fr \
--cc=emacs-devel@gnu.org \
--cc=mvoteiza@udel.edu \
/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.