From: storm@cua.dk (Kim F. Storm)
Cc: harder@ifa.au.dk, emacs-devel@gnu.org, monnier@iro.umontreal.ca,
handa@m17n.org, "Kim F. Storm" <storm@cua.dk>
Subject: Re: M-x grep is too slow
Date: 21 Jul 2004 10:36:22 +0200 [thread overview]
Message-ID: <m3r7r5aha1.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <E1Bn1S2-0005DV-6Q@fencepost.gnu.org>
Richard Stallman <rms@gnu.org> writes:
> > Do you mean caching at the Lisp level inside Font-Lock mode?
> > That might be easy to do.
>
> I was thinking about doing it explicitly in compile.el...
>
> Is this slowness in font-lock or is it in compile.el?
I don't really know.
The code that calls previous-single-property-change is in compile.el,
but it could be that the code is actually called by font-lock.
In any case, the 'message and 'directory properties are local to
compile.el, so I would suppose that the caching (if possible)
would have to be done in compile.el.
Maybe someone who better understands the new compile.el could comment
on this.
next prev parent reply other threads:[~2004-07-21 8:36 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 [this message]
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=m3r7r5aha1.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--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 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).