all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: harder@ifa.au.dk, emacs-devel@gnu.org, monnier@iro.umontreal.ca,
	handa@m17n.org
Subject: Re: M-x grep is too slow
Date: Sat, 17 Jul 2004 07:54:13 -0400	[thread overview]
Message-ID: <E1Blnld-00072u-CG@fencepost.gnu.org> (raw)
In-Reply-To: <m3n0200zvr.fsf@kfs-l.imdomain.dk> (storm@cua.dk)

    Looking with a debugger, a lot of time is spent in
    previous-single-property-change.

    Maybe caching the last position of `directory' and `message' properties
    would make a difference ?

Do you mean caching at the Lisp level inside Font-Lock mode?
That might be easy to do.

Where is previous-single-property-change being called from?
Maybe a change there is what we need.


Aside from that, I have a feeling it is wrong for Compilation
mode to turn on Font-Lock mode by default.  This nonuniformity
in the control of Font-Lock mode seems wrong.

  reply	other threads:[~2004-07-17 11:54 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 [this message]
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

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

  git send-email \
    --in-reply-to=E1Blnld-00072u-CG@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.org \
    --cc=harder@ifa.au.dk \
    --cc=monnier@iro.umontreal.ca \
    /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.