unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: no-spam@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: font-lock has become far too slow
Date: 29 Apr 2004 01:07:28 +0200	[thread overview]
Message-ID: <m3hdv34s7j.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <m265bljb1n.fsf@Majnun.local>

John Wiegley <johnw@gnu.org> writes:

> John Wiegley <johnw@gnu.org> writes:
> 
> > Starting very recently, font-lock (using jit-lock) has become so
> > slow that Emacs can no longer keep up with my typing -- on a modern,
> > 1.25 GHz PowerBook G4.  I haven't profiled things yet, so does
> > anyone know what was added that might make things this slow?  I
> > compiled with -O3 -fomit-frame-pointer, but still am forced to turn
> > off font-lock mode.
> 
> It looks like it's more than just font-lock.  With font-lock off, if I
> hold down C-p to move up in the buffer, drawing new pages takes up to
> a full second (subjective).  And typing past the end of a line has a
> hard time keeping up with my typing.  Even typing this message is very
> laggy.  I will have to do some profiling to see what it going on.
> Nothing in my configuration has changed very drastically since
> February, when things were working quite nicely.

I just installed a fix for a problem causing excessive redisplay.

Please see if this problem has been fixed as well.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  parent reply	other threads:[~2004-04-28 23:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-27 22:31 font-lock has become far too slow John Wiegley
2004-04-27 22:44 ` John Wiegley
2004-04-28  6:20   ` Eli Zaretskii
2004-04-29 22:08     ` John Wiegley
2004-05-03 19:53       ` Kevin Rodgers
2004-05-03 21:30         ` Stefan Monnier
2004-04-28 23:07   ` Kim F. Storm [this message]
2004-04-29 22:08     ` John Wiegley

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=m3hdv34s7j.fsf@kfs-l.imdomain.dk \
    --to=no-spam@cua.dk \
    --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).