all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 24802@debbugs.gnu.org
Subject: bug#24802: emacs -Q -nw loads cl-lib
Date: Mon, 31 Oct 2016 17:45:16 +0200	[thread overview]
Message-ID: <83funcplo3.fsf@gnu.org> (raw)
In-Reply-To: <izoa21mm7t.fsf@fencepost.gnu.org> (message from Glenn Morris on Sun, 30 Oct 2016 19:49:26 -0400)

> From: Glenn Morris <rgm@gnu.org>
> Cc: 24802@debbugs.gnu.org
> Date: Sun, 30 Oct 2016 19:49:26 -0400
> 
> As you said in
> 
> http://lists.gnu.org/archive/html/emacs-devel/2015-10/msg00095.html
> 
>     Up until now, the rules for pre-loading package X were that either
>     (a) some preloaded package requires X, or (b) X will be
>     auto-loaded at the beginning of every session by some very
>     frequent operation, like visiting the first file or creating a
>     window or a frame.
> 
> Here we have case b), without needing any operation at all.
> 
> OK, it's not "every session", it's "every -nw session in an
> xterm-like terminal", but IMO the same should apply.
> 
> [1] I don't count the actual term/*.el files themselves in this,
> because those that aren't preloaded have traditionally been trivial.
> Perhaps xterm.el has become so large, and is used (I guess) in such a
> large fraction of without-x builds, that it should be preloaded in
> such builds, as x-win.el is in with-x builds. I think that's a
> separate issue though. It would however make the issue in this report
> obvious.

That's exactly my line of reasoning: as long as we don't preload
xterm.el, we shouldn't regard its loading of other files a problem.





  reply	other threads:[~2016-10-31 15:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-26 16:40 bug#24802: emacs -Q -nw loads cl-lib Glenn Morris
2016-10-26 18:34 ` Eli Zaretskii
2016-10-30 23:49   ` Glenn Morris
2016-10-31 15:45     ` Eli Zaretskii [this message]
2017-09-02 13:31       ` Eli Zaretskii

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=83funcplo3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24802@debbugs.gnu.org \
    --cc=rgm@gnu.org \
    /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.