From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Strange byte-compiler output
Date: Wed, 28 Nov 2001 12:10:48 -0500 [thread overview]
Message-ID: <2n667u6ctj.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: <vaf8zcuc6oh.fsf@lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Mon, 26 Nov 2001 08:50:06 +0100")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Look here:
>
> /----
> | Wrote /home-local/grossjoh/lisp/gnus/lisp/mailcap.elc
> | Loading gnus-group...
> | Loading gnus-group...
> | Loading gnus-group...
> | Loading gnus-group...
> | Wrote /home-local/grossjoh/lisp/gnus/lisp/message.elc
> \----
>
> This is part of the output from "make". How come it loads gnus-group
> four times during compilation of mailcap?
The output is from compilation of message.el where functions
gnus-group-name-decode and gnus-group-name-charset are used. But they
are autoloaded and defsubst'ed. I've fixed the problem.
ShengHuo
prev parent reply other threads:[~2001-11-28 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 7:50 Kai Großjohann
2001-11-28 17:10 ` ShengHuo ZHU [this message]
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=2n667u6ctj.fsf@zsh.cs.rochester.edu \
--to=zsh@cs.rochester.edu \
/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.
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 NNTP newsgroup(s).