all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: rms@gnu.org
Cc: bug-cc-mode@gnu.org, acm@muc.de,
	Dave Milter <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 00:52:04 -0500	[thread overview]
Message-ID: <87mye5kmm3.fsf@cyd.mit.edu> (raw)
In-Reply-To: <E1LJzNu-0007Y4-Sa@fencepost.gnu.org> (Richard M. Stallman's message of "Mon, 05 Jan 2009 19:01:26 -0500")

Richard M Stallman <rms@gnu.org> writes:

> 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.  There are certain
special situations in which a C-mode slowdown is observable, but it
should be fine in normal usage, at least in my experience (I am using a
fairly slow Pentium IV, and do not experience C-mode slowness when
editing the Emacs source code).




  reply	other threads:[~2009-01-06  5:52 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 [this message]
2009-01-06 22:59         ` Richard M Stallman
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mye5kmm3.fsf@cyd.mit.edu \
    --to=cyd@stupidchicken.com \
    --cc=acm@muc.de \
    --cc=bug-cc-mode@gnu.org \
    --cc=davemilter@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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.