From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: stefan@marxist.se, emacs-devel@gnu.org
Subject: Re: Preloading seq.el
Date: Thu, 29 Aug 2019 18:20:23 +0300 [thread overview]
Message-ID: <834l20athk.fsf@gnu.org> (raw)
In-Reply-To: <878srcj94g.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 29 Aug 2019 17:15:27 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: stefan@marxist.se, emacs-devel@gnu.org
> Date: Thu, 29 Aug 2019 17:15:27 +0200
>
> > I'm probably missing something, because I don't understand how using
> > SOMETHING.el from a preloaded code would necessarily requore
> > preloading SOMETHING.el as well. Isn't autoloading working?
>
> Oh, I didn't think slapping ;;;###autoload cookies on all the functions
> in seq/cl-lib was on the table, but if it is, that's a solution, too.
I don't know if we want all of them to be autoloaded, but I see no
reason not to autoload some, those which are used by preloaded code.
> By the way, I summed up the size of the .elc files loadup.el today does,
> and it's over 3MB. seq/cl-lib.elc is 56KB. So we're talking about
> preloading less than 2% more .elc code. And there's 242 .el files that
> require seq/cl-lib, so I think it's unlikely that many users don't end
> up with loading seq/cl-lib, anyway, no matter what they do beyond
> starting "emacs -Q".
The way to hell is paced one step at a time. Those 3MB were not all
added in one go, they were added one file at a time. So we need to
examine every single file we want to add and decide on a case by case
basis, otherwise we will get 6MB instead of 3MB faster than you can
say "make autoloads".
next prev parent reply other threads:[~2019-08-29 15:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 12:21 Preloading seq.el Stefan Kangas
2019-08-29 12:30 ` Lars Ingebrigtsen
2019-08-29 12:47 ` Eli Zaretskii
2019-08-29 12:50 ` Lars Ingebrigtsen
2019-08-29 14:59 ` Eli Zaretskii
2019-08-29 15:15 ` Lars Ingebrigtsen
2019-08-29 15:20 ` Eli Zaretskii [this message]
2019-08-29 15:35 ` Lars Ingebrigtsen
2019-08-29 18:41 ` Eli Zaretskii
2019-08-29 18:43 ` Lars Ingebrigtsen
2019-08-29 21:44 ` Stefan Monnier
2019-08-29 15:20 ` Stefan Monnier
2019-08-29 12:44 ` Eli Zaretskii
2019-08-31 12:33 ` Zhu Zihao
2019-08-31 12:38 ` Eli Zaretskii
2019-09-06 0:49 ` Juanma Barranquero
2019-09-06 7:12 ` Eli Zaretskii
2019-09-06 7:46 ` Robert Pluim
2019-09-06 8:23 ` Eli Zaretskii
2019-09-06 11:27 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834l20athk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=stefan@marxist.se \
/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.