unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: emacs-devel@gnu.org
Subject: Re: Preloading seq.el
Date: Thu, 29 Aug 2019 15:44:47 +0300	[thread overview]
Message-ID: <838srcb0ow.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmmCxSn4_NqyO2mR1wRnXeG11_zWsDnUAuwYpSLGtaqULA@mail.gmail.com> (message from Stefan Kangas on Thu, 29 Aug 2019 14:21:00 +0200)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Thu, 29 Aug 2019 14:21:00 +0200
> 
> Could we preload seq.el?
> 
> Previous discussion here:
> https://lists.gnu.org/archive/html/emacs-devel/2016-07/msg00852.html
> 
> In the previous discussion someone said that we would be punishing
> users that do not use it if we preloaded it.  It's not clear to me how
> this would punish users.

By enlarging the memory footprint of a running Emacs more than
necessary.

> Stefan Monnier also pointed out that seq.el depends on cl-lib, and
> that to preload seq, we would need to preload cl-lib.  This seems to
> be due to a single use of the  cl-subseq function in cl-extra.el.  If
> this is a show stopper, perhaps we could see if we can get rid of that
> single use.

I don't yet understand what problems do you have with having the
necessary functions from seq.el autoloaded.  Is the code you are
writing for help.el meant to run in every Emacs session right at its
beginning?  If not, why autoloading is not the solution?



  parent reply	other threads:[~2019-08-29 12:44 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
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 [this message]
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

  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=838srcb0ow.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.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 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).