unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: master f225011: ibuffer-do-isearch: don't depend on `cl-values-list' (bug#38430)
Date: Mon, 2 Dec 2019 18:18:35 +0100	[thread overview]
Message-ID: <CAAeL0SS9po5QT8e-FE-6Ezv0DJYMq+gmkeXRabXTyhxzADYgdw@mail.gmail.com> (raw)
In-Reply-To: <8336e2n3fd.fsf@gnu.org>

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

On Mon, Dec 2, 2019 at 4:38 PM Eli Zaretskii <eliz@gnu.org> wrote:

> Yes, we don't preload packages just because it's convenient.

Oh, well, sorry I was unclear. I was not asking about that. I said that IMO
we should preload cl-lib, but I know that's... unwanted.

What I'm really asking is what is our stance regarding using cl-lib in
lisp/*. I mean, are we trying to minimize run-time dependencies on cl-lib,
or it is ok to use freely?

TIA,

    Juanma

[-- Attachment #2: Type: text/html, Size: 656 bytes --]

  reply	other threads:[~2019-12-02 17:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191201091356.26612.95511@vcs0.savannah.gnu.org>
     [not found] ` <20191201091358.11752207E0@vcs0.savannah.gnu.org>
2019-12-01 18:29   ` master f225011: ibuffer-do-isearch: don't depend on `cl-values-list' (bug#38430) Stefan Monnier
2019-12-01 23:36     ` Juanma Barranquero
2019-12-02  0:39       ` Juanma Barranquero
2019-12-02  1:55       ` Stefan Monnier
2019-12-02  2:20         ` Juanma Barranquero
2019-12-02  3:40           ` Eli Zaretskii
2019-12-02  3:43             ` Juanma Barranquero
2019-12-02 15:38               ` Eli Zaretskii
2019-12-02 17:18                 ` Juanma Barranquero [this message]
2019-12-02 17:40                   ` Eli Zaretskii
2019-12-02 18:10                     ` Juanma Barranquero

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=CAAeL0SS9po5QT8e-FE-6Ezv0DJYMq+gmkeXRabXTyhxzADYgdw@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).