unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: What's your favourite *under_publicized* editing feature of Emacs?
Date: Tue, 08 Feb 2011 23:37:20 -0500	[thread overview]
Message-ID: <jwvy65prfx1.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: mailman.11.1297206657.16135.help-gnu-emacs@gnu.org

>> I set 'grep-mode' on my log file (which follow GNU
>> error coding convention). On 50-100 KiB logs it take
>> 10 sec to highlight matches. On larger files I type
>> C-g to stop matching for highlighting.

You may want to try the Emacs trunk's version of compile.el (I think
it'll work with Emacs-23 as well).  It should help out by being more
lazy (e.g. it'll still takes 10s to parse the file when you jump to the
end of it, but it should open instantaneously because it'll only need to
parse the first page for that).

> And I realize that compilation-mode is dumb as it try
> set on all matched file/line pairs text properties to
> allow move to another file by RET.

compilation-mode indeed does more work than I'd like at the "highlight"
time, and some of that work could indeed be delayed to the moment the
user hits RET on a line.  But my impression is that most of the time is
spent regexp-matching (i.e. looking for matches) anyway, so moving this
work won't make much difference if any.  IOW my impression is that if
your code is faster it's because it uses either more efficient regexps,
or fewer regexps.

>     ("^\\([^:]+\\):\\([[:digit:]]+\\):[^

E.g. this regexp is more efficient than the one used by grep.el, by
disallowing : in file names (resulting in a backtrack-free regexp).


        Stefan


  parent reply	other threads:[~2011-02-09  4:37 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.0.1296117403.8303.help-gnu-emacs@gnu.org>
2011-01-28  9:54 ` What's your favourite *under_publicized* editing feature of Emacs? Simón Ortiz
2011-01-28 21:22   ` Ken Goldman
     [not found]   ` <mailman.21.1296249764.1176.help-gnu-emacs@gnu.org>
2011-01-28 22:59     ` Stefan Monnier
2011-01-29 14:46       ` Oleksandr Gavenko
2011-01-29 15:00         ` Eli Zaretskii
2011-01-29 15:02         ` Perry Smith
     [not found]         ` <mailman.10.1296313340.8933.help-gnu-emacs@gnu.org>
2011-01-29 16:08           ` Stefan Monnier
2011-02-17 10:53           ` Giorgos Keramidas
2011-02-17 13:43             ` Perry Smith
2011-02-17 14:01               ` Thien-Thi Nguyen
     [not found]               ` <mailman.9.1297951684.6316.help-gnu-emacs@gnu.org>
2011-02-17 19:04                 ` view/edit large files (was: What's your favourite *under_publicized* editing feature of Emacs?) Ted Zlatanov
2011-02-18  0:09             ` What's your favourite *under_publicized* editing feature of Emacs? Tim X
2011-01-29 12:55 ` Javier Sanz
2011-02-06 20:11   ` Oleksandr Gavenko
2011-02-08 23:10     ` Oleksandr Gavenko
     [not found]     ` <mailman.11.1297206657.16135.help-gnu-emacs@gnu.org>
2011-02-09  4:37       ` Stefan Monnier [this message]
2011-02-09 20:51         ` Oleksandr Gavenko
2011-02-09 21:31         ` Oleksandr Gavenko
2011-02-09 22:32           ` Thien-Thi Nguyen
2011-02-14 20:44             ` Oleksandr Gavenko
     [not found]         ` <mailman.10.1297284733.9144.help-gnu-emacs@gnu.org>
2011-02-10 17:24           ` Stefan Monnier
2011-03-01 21:30 What's your favourite *under_publicized* editing feature ofEmacs? Cthun
2011-03-02  1:00 ` What's your favourite *under_publicized* editing feature of Emacs? Steve
2011-03-02  5:34   ` PJ Weisberg
  -- strict thread matches above, loose matches on Subject: below --
2011-01-27  8:33 Le Wang
2011-01-27  9:29 ` Deniz Dogan
2011-01-27 12:03 ` Wang Lei
2011-01-27 14:13   ` suvayu ali
2011-01-27 14:12 ` Ken Goldman
2011-01-27 18:11 ` Erik Iverson
     [not found] ` <mailman.0.1296137574.27610.help-gnu-emacs@gnu.org>
2011-01-27 22:23   ` Joe Fineman
2011-01-28  6:40     ` Jason Rumney

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=jwvy65prfx1.fsf-monnier+gnu.emacs.help@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=help-gnu-emacs@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.
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).