From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: nicolas@petton.fr, emacs-devel@gnu.org, tino.calancha@gmail.com
Subject: Re: Add autoload cookies in seq.el
Date: Wed, 20 Jul 2016 18:13:28 +0300 [thread overview]
Message-ID: <83mvlcz6jr.fsf@gnu.org> (raw)
In-Reply-To: <m3wpkg4f4e.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 20 Jul 2016 15:24:01 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Tino Calancha <tino.calancha@gmail.com>, nicolas@petton.fr, emacs-devel@gnu.org
> Date: Wed, 20 Jul 2016 15:24:01 +0200
>
> But I find it rather odd that we can't use the best and most modern
> libraries in the most central parts of Emacs. That's kinda backwards.
> The most central parts of Emacs gets the most obfuscated code?
Are we mis-communicating? If somefile.el needs a function that is in
subr-x.el, all it has to do is (require subr-x). How's that a
problem?
> Not dumping seq with Emacs seems rather odd, because it's going to get
> used a while lot. That's the point of having a library like that.
When/if seq.el will become used so much that it will almost always
immediately load at the beginning of a session, we will indeed add it
to preloaded ones. But as long as that doesn't happen, why should we
punish those users who have no use for seq?
next prev parent reply other threads:[~2016-07-20 15:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 6:06 Add autoload cookies in seq.el Tino Calancha
2016-05-20 8:26 ` Nicolas Petton
2016-05-20 8:54 ` Tino Calancha
2016-05-20 9:42 ` Eli Zaretskii
2016-05-21 0:07 ` Tino Calancha
2016-05-21 6:50 ` Eli Zaretskii
2016-07-20 13:24 ` Lars Ingebrigtsen
2016-07-20 15:13 ` Eli Zaretskii [this message]
2016-07-21 10:51 ` Lars Ingebrigtsen
2016-07-21 13:27 ` Ted Zlatanov
2016-07-21 14:38 ` Eli Zaretskii
2016-07-21 14:33 ` Eli Zaretskii
2016-07-21 15:01 ` Lars Ingebrigtsen
2016-07-21 16:09 ` Eli Zaretskii
2016-07-22 9:04 ` Lars Ingebrigtsen
2016-07-22 10:50 ` Ted Zlatanov
2016-07-21 14:36 ` Michael Heerdegen
2016-07-21 15:45 ` Stefan Monnier
2016-07-22 14:26 ` Stefan Monnier
2016-07-22 15:07 ` Nicolas Petton
2016-07-22 15:18 ` Stefan Monnier
2016-07-22 15:28 ` Eli Zaretskii
2016-07-22 17:48 ` Nicolas Petton
2016-05-22 12:17 ` Tino Calancha
2016-05-22 19:54 ` Nicolas Petton
2016-05-23 1:49 ` Tino Calancha
2016-05-23 8:33 ` Nicolas Petton
2016-05-23 15:13 ` Paul Eggert
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=83mvlcz6jr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=nicolas@petton.fr \
--cc=tino.calancha@gmail.com \
/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).