X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Date: Fri, 24 Jul 2009 18:57:57 +0300
From: Eli Zaretskii <eliz AT gnu DOT org>
Subject: Re: Emacs pretest 23.0.96 is available
In-reply-to: <h4c5fa$2m2$1@news.onet.pl>
To: djgpp AT delorie DOT com
Message-id: <83ljme3wfu.fsf@gnu.org>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-2
Content-transfer-encoding: QUOTED-PRINTABLE
X-012-Sender: halo1 AT inter DOT net DOT il
References: <83eislssg7 DOT fsf AT gnu DOT org> <h44g99$ofl$1 AT news DOT onet DOT pl> <83bpnd6gvi DOT fsf AT gnu DOT org> <h46dkh$svh$1 AT news DOT onet DOT pl> <831vo8620b DOT fsf AT gnu DOT org> <e7a38c41-004a-40b2-a7b5-6b51acf0e47a AT d4g2000yqa DOT googlegroups DOT com> <83my6v43p3 DOT fsf AT gnu DOT org> <d4a932df-8e49-4550-9857-bbc45cc27f35 AT q11g2000yqi DOT googlegroups DOT com> <h4c5fa$2m2$1 AT news DOT onet DOT pl>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: "Tomasz Zbro=BFek" <t DOT zbrozek AT upos DOT com DOT pl>
> Date: Fri, 24 Jul 2009 11:21:15 +0000 (UTC)
>=20
> I talk about emacs *.c files like malloc.c or buffer.c.
> When I start emacs and load first file (e.g malloc.c) it takes 2-3 =
seconds
> to be loaded with font-lock-mode enabled. But when I load second fi=
le=20
> (buffer.c which is even bigger) it takes only about 1 second. I not=
iced=20
> that only loading first file takes more time, next files load much =
faster.

This is normal: the first time you visit a .c file, Emacs loads the
CC-Mode package that supports editing C and C++ source files.  CC-Mod=
e
is quite large, so it takes some time to load.  You can see that by
evaluating "(featurep 'cc-mode)" before and after you visit the first
=2Ec file.

In previous versions of Emacs, loading Lisp libraries was always
announced in the echo area, so you'd see that and understand the
delay.  But in Emacs 23, it was decided (against my objections, FWIW)
to suppress these messages, so now the user has no clue.