From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: harder@ifa.au.dk, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: M-x grep is too slow
Date: 13 Jul 2004 13:46:04 -0400 [thread overview]
Message-ID: <jwv3c3vg62x.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <200407130036.JAA04111@etlken.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.
I see it also. Grep's output at first comes in fast and then at some point
it abruptly slows down and then it only comes in a couple chars at a time
(with enough time inbetween to see the steps). Later on it switched again
to "fast" mode, and then switched again to "slow" mode, etc...
The problem is not the time taken in font-lock, but the fact that the text
gets inserted one char at a time (or maybe 2 or 3 chars, but it should not
happen that way; and as a matter of fact it does not happen that way when
grep's output comes in fast).
It seems related to the problem David had with AUCTeX on uniprocessors
running the Linux kernel with the "interactive" scheduler. Kim installed
a patch to fix it, but maybe the patch isn't doing its job here for
some reason.
Stefan "running on a uniprocessor Linux kernel"
next prev parent reply other threads:[~2004-07-13 17:46 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 [this message]
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=jwv3c3vg62x.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=harder@ifa.au.dk \
--cc=rms@gnu.org \
/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).