unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
Cc: harder@ifa.au.dk, emacs-devel@gnu.org
Subject: Re: M-x grep is too slow
Date: Tue, 13 Jul 2004 07:00:58 +0200	[thread overview]
Message-ID: <3405-Tue13Jul2004070058+0300-eliz@gnu.org> (raw)
In-Reply-To: <200407130036.JAA04111@etlken.m17n.org> (message from Kenichi Handa on Tue, 13 Jul 2004 09:36:47 +0900 (JST))

> Date: Tue, 13 Jul 2004 09:36:47 +0900 (JST)
> From: Kenichi Handa <handa@m17n.org>
> 
> I tried the above but it finished quite soon.   But, when I tried:
> 
>         M-x grep -nH -e while emacs/lisp/*/*.el
> 
> it took long time.  So, I turned off global-font-lock-mode
> and tried again.  But, *grep* buffer is fontified.   Isn't
> it a bug?  Anyway, I tried this:
> 
> (add-hook 'grep-mode-hook #'(lambda () (font-lock-mode -1)))
> 
> Then the above grep also finished quite soon.  So, yes,
> font-lock seems to be the culprit.

Perhaps instrumenting font-lock with elp and running the same test
will show what part(s) of font-lock cause this.

  reply	other threads:[~2004-07-13  5:00 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 [this message]
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

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=3405-Tue13Jul2004070058+0300-eliz@gnu.org \
    --to=eliz@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).