unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicolas Petton <nicolas@petton.fr>
To: Juri Linkov <juri@linkov.net>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Making seq.el an Elpa core package?
Date: Mon, 04 Mar 2019 23:42:46 +0100	[thread overview]
Message-ID: <87k1hexnvd.fsf@petton.fr> (raw)
In-Reply-To: <87o96qtn6i.fsf@mail.linkov.net>

[-- Attachment #1: Type: text/plain, Size: 950 bytes --]

Juri Linkov <juri@linkov.net> writes:

> This package is so useful that it should be preloaded in loadup.el.

As of today seq.el requires cl-lib, but I think I could easily get rid
of the dependency.  Anyway IIRC this was discussed some years ago when I
started working on seq.el, and at the time I also thought such a library
should come preloaded, but the opinion on this list was quite divided.

> It introduces to Elisp programming many necessary idioms that are
> expected from any modern programming language to help writing more
> clear and readable code.

Thanks, I'm glad you like it :-)

> Recently I implemented a new feature for isearch using seq.el.
> The resulting code is much shorter with seq than it would be
> when using ugly old style like `(delq nil (mapcar ...))'.
>
> But I can't submit a patch for isearch.el because currently
> seq.el is not loaded by default.

Oh right, because isearch.el is itself preloaded.

Cheers,
Nico

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2019-03-04 22:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04 12:18 Making seq.el an Elpa core package? Nicolas Petton
2019-03-04 20:51 ` Juri Linkov
2019-03-04 22:42   ` Nicolas Petton [this message]
2019-03-10 11:48     ` Phillip Lord
2019-03-10 13:04       ` Eli Zaretskii
2019-03-11 22:54         ` Phillip Lord
2019-03-12  2:29           ` Stefan Monnier
2019-03-12 16:48 ` Stefan Monnier
2019-03-13  8:43   ` 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=87k1hexnvd.fsf@petton.fr \
    --to=nicolas@petton.fr \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    /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).