unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 22669@debbugs.gnu.org
Subject: bug#22669: loading term/xterm.elc loads cl-lib at runtime
Date: Mon, 15 Feb 2016 21:55:59 +0200	[thread overview]
Message-ID: <83si0twxww.fsf@gnu.org> (raw)
In-Reply-To: <ifoabhetbq.fsf@fencepost.gnu.org> (message from Glenn Morris on Mon, 15 Feb 2016 13:12:25 -0500)

> From: Glenn Morris <rgm@gnu.org>
> Cc: 22669@debbugs.gnu.org
> Date: Mon, 15 Feb 2016 13:12:25 -0500
> 
> Eli Zaretskii wrote:
> 
> >> Loading term/xterm.elc loads cl-lib at runtime.
> >> This means that cl-lib is loaded at startup in "emacs -Q -nw", which is
> >> undesirable.
> >
> > Why is that undesirable?
> >
> > How is xterm.el different from any other package which requires
> > cl-lib?
> 
> This was explained in http://debbugs.gnu.org/22613#45

Sorry, I don't see any explanation there.  What I do see is the fact
that we treat lisp/term/* files specially.  I agree with that, since
these files are only loaded at startup when needed, so they are not
something "emacs -Q" "needs".

I also see there a suggestion to figure out why cl-lib gets loaded,
and I believe this part is now complete.

> Also in this particular case, it can create the mistaken impression that
> cl-lib is always available, which I think leads to some of the ongoing
> confusion in bug#22613.

OK, but that doesn't sound like a problem we need to fix in the code.

So my vote is not to fix this one.





  reply	other threads:[~2016-02-15 19:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-14 22:57 bug#22669: loading term/xterm.elc loads cl-lib at runtime Glenn Morris
2016-02-15  3:37 ` Eli Zaretskii
2016-02-15 18:12   ` Glenn Morris
2016-02-15 19:55     ` Eli Zaretskii [this message]
2016-02-16  6:34       ` Glenn Morris
2016-02-16 15:55         ` 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

  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=83si0twxww.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22669@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 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).