From: Richard M Stallman <rms@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: bug-cc-mode@gnu.org, acm@muc.de, davemilter@gmail.com,
emacs-devel@gnu.org
Subject: Re: open large file with C code: is it realy should be so slow?
Date: Tue, 06 Jan 2009 17:59:39 -0500 [thread overview]
Message-ID: <E1LKKtf-0008EJ-AF@fencepost.gnu.org> (raw)
In-Reply-To: <87mye5kmm3.fsf@cyd.mit.edu> (message from Chong Yidong on Tue, 06 Jan 2009 00:52:04 -0500)
> I too find C mode painfully slow these days. I wonder what changed to
> make it so much slower than it was. Perhaps the only relevant change
> is that Font Lock is now enabled; I never used to enable it. Even so,
> it must make a lot of users unhappy.
You are likely using an exceptionally slow computer.
I am using a Lemote Yeeloong, which could well be the machine
we will recommend to the public for the coming year or more.
I just did some testing and I am obliged to modify my complaint.
It seems that the slowness is mainly in _loading_ C mode.
Visiting buffer.h, when it is the first C file I visit,
just took 20 seconds. However, once C mode is loaded,
visiting buffer.h again is pretty fast.
------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
next prev parent reply other threads:[~2009-01-06 22:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 10:01 open large file with C code: is it realy should be so slow? Dave Milter
2008-12-01 12:37 ` Alan Mackenzie
2009-01-04 22:07 ` Dave Milter
2009-01-04 23:31 ` Alan Mackenzie
2009-11-01 17:01 ` Dave Milter
2009-01-06 0:01 ` Richard M Stallman
2009-01-06 5:52 ` Chong Yidong
2009-01-06 22:59 ` Richard M Stallman [this message]
2009-01-07 1:16 ` Chong Yidong
2009-01-08 11:37 ` Richard M Stallman
2009-01-08 12:42 ` Alan Mackenzie
2009-01-06 19:03 ` Alan Mackenzie
2009-01-06 21:50 ` Stefan Monnier
2009-12-04 15:25 ` Alan Mackenzie
2009-12-19 10:51 ` Dave Milter
2009-12-27 10:33 ` Dave Milter
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=E1LKKtf-0008EJ-AF@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=acm@muc.de \
--cc=bug-cc-mode@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=davemilter@gmail.com \
--cc=emacs-devel@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).