unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Toon Claes <toon@tonotdo.com>
Cc: "10652@debbugs.gnu.org" <10652@debbugs.gnu.org>
Subject: bug#10652: font-lock very slow for C++
Date: Thu, 29 Mar 2012 22:00:26 +0000	[thread overview]
Message-ID: <20120329220026.GC2594@acm.acm> (raw)
In-Reply-To: <79C7C145-A878-4C38-9B5F-95DFC30C68CD@tonotdo.com>

Hello, Toon.

On Thu, Mar 29, 2012 at 09:46:03PM +0200, Toon Claes wrote:
> Hi Alan,

> About:
> (i) yes I've tried that, emacs -Q didn't make a difference

Worth knowing

> (ii) I am using emacs from git, commit 2ac37884107bd4e78bb… Should I
> get it from the bazaar repo?

I'm not familiar with the git repository.  If the revision is recent
(within the last week or two or three) it should be OK.  I just wanted to
check you weren't using a 6-month old version.

> (iii) I know font-lock has nothing to do with isearch. When I disable
> font-lock-mode for the buffer, isearch does not hang. So the issue
> isn't isearch. Sorry I created some confusion in previous mail.

OK.  What I suspect is that the isearch works fine, then the
fontification hangs before the screen can redisplay.  How long does it
hang for?  Any chance you could perhaps leave it hanging over lunchtime,
or perhaps even overnight to see if it might just be _very_ slow.

Could you perhaps try disabling font-lock, doing the isearch, then
enabling font-lock again.  Does it then still hang, or does it come up
OK?

Lastly, is there anything unusual about your test file.  Perhaps long
regions of text which contain no semicolons or maybe no braces?  Or maybe
hundreds of macro definitions one after the other, something like that?

> Toon

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2012-03-29 22:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30 11:15 bug#10652: 24.0.93; font-lock very slow for C++ Helmut Eller
2012-02-26  9:47 ` Chong Yidong
2012-03-01 19:36   ` Alan Mackenzie
2012-03-02 22:27   ` Alan Mackenzie
2012-03-16 14:19   ` Alan Mackenzie
2012-03-14  9:45 ` bug#10652: " Toon Claes
2012-03-16 10:18   ` bug#10652: Recursive loop in alloc.c [ Was: font-lock very slow for C++ ] Alan Mackenzie
     [not found]   ` <20120316101838.GB3439@acm.acm>
2012-03-16 10:34     ` Andreas Schwab
2012-03-16 14:24 ` bug#10652: 24.0.93; font-lock very slow for C++ Alan Mackenzie
2012-03-28  7:07 ` bug#10652: " Toon Claes
2012-03-29  9:35   ` Alan Mackenzie
2012-03-29 19:46     ` Toon Claes
2012-03-29 22:00       ` Alan Mackenzie [this message]
2012-04-02  7:48         ` Toon Claes

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=20120329220026.GC2594@acm.acm \
    --to=acm@muc.de \
    --cc=10652@debbugs.gnu.org \
    --cc=toon@tonotdo.com \
    /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).