unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: harder@ifa.au.dk, emacs-devel@gnu.org
Subject: Re: M-x grep is too slow
Date: Tue, 13 Jul 2004 20:17:53 -0400	[thread overview]
Message-ID: <E1BkXT7-0005zd-HA@fencepost.gnu.org> (raw)
In-Reply-To: <E1BkAgT-0000zL-9a@fencepost.gnu.org> (message from Richard Stallman on Mon, 12 Jul 2004 19:58:09 -0400)

I am not surprised that font-lock is responsible, but we need to
find out what it's doing that takes so long.

If you follow my suggestion to run under GDB, type C-z, and then type
xbacktrace, you'll find out which functions of font-lock mode
are running most of the time.  If you put a call to (debug) in
one of them, you can step through it and see whether it takes
a long time, and what it is doing.

It would be useful to check whether the font lock keywords
used for compile mode have changed in the past few months.
If so, that change might be at fault.

      parent reply	other threads:[~2004-07-14  0:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3fz87bj8l.fsf@defun.localdomain>
     [not found] ` <E1BhWlL-0007Mq-Ns@fencepost.gnu.org>
     [not found]   ` <m3n02a2uo4.fsf@defun.localdomain>
     [not found]     ` <E1Bixsv-0001wJ-G8@fencepost.gnu.org>
     [not found]       ` <m3brim8m2r.fsf@defun.localdomain>
2004-07-12 23:58         ` M-x grep is too slow Richard Stallman
2004-07-13  0:36           ` Kenichi Handa
2004-07-13  5:00             ` Eli Zaretskii
2004-07-13 17:46             ` Stefan Monnier
2004-07-16 14:51               ` Kim F. Storm
2004-07-17 11:54                 ` Richard Stallman
2004-07-19 14:46                   ` Kim F. Storm
2004-07-20 20:43                     ` Richard Stallman
2004-07-21  8:36                       ` Kim F. Storm
2004-07-22 21:36                         ` Richard Stallman
2004-07-14  0:18             ` Richard Stallman
2004-07-14  0:17           ` Richard Stallman [this message]

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=E1BkXT7-0005zd-HA@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=harder@ifa.au.dk \
    /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).