From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Daniel Colascione <dan.colascione@gmail.com>
Cc: Lars Hamren <hamren@sdu.se>, 7069@debbugs.gnu.org
Subject: bug#7069: Compilation from within emacs becomes slower and slower until Emacs is restarted
Date: Mon, 25 Apr 2011 09:28:18 -0300 [thread overview]
Message-ID: <jwvwrii348v.fsf-monnier+INBOX@gnu.org> (raw)
In-Reply-To: <4DB4CB8A.80607@gmail.com> (Daniel Colascione's message of "Sun, 24 Apr 2011 18:16:58 -0700")
>>> (add-hook 'compilation-mode-hook
>>> (lambda () (setq compilation-error-regexp-alist
>>> (cons
>>> ;; Quartus II error messages
>>> '(".*Verilog .* at \\(.+\\)(\\([0-9]+\\)): .*" 1 2)
>>> compilation-error-regexp-alist))))
> [snip]
>>> I haven't looked further into why this should be a problem.
>>
>> I can't think of any reason why this regexp should make compilation
>> become slower (I can see why it would make it slow, but unless lines
>> become longer over time, it should keep the same slowness at the end as
>> it had at the beginning).
> He's adding an entry to compilation-error-regexp-alist every time he
> compiles,
Duh, good catch, thank you,
Stefan
next prev parent reply other threads:[~2011-04-25 12:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-19 0:38 bug#7069: Compilation from within emacs becomes slower and slower until Emacs is restarted Lars Hamren
2010-09-19 18:14 ` bug#7069: Problem only with "compile", not with "shell-command" Lars Hamren
2010-09-19 18:32 ` bug#7069: Clarification Lars Hamren
2010-09-22 6:43 ` bug#7069: Compilation from within emacs becomes slower and slower until Emacs is restarted Jan Djärv
2010-10-28 2:42 ` Stefan Monnier
2011-04-20 10:04 ` Lars Hamren
2011-04-20 13:10 ` Stefan Monnier
2011-04-25 1:16 ` Daniel Colascione
2011-04-25 12:28 ` Stefan Monnier [this message]
2011-04-25 13:05 ` Lars Hamren
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=jwvwrii348v.fsf-monnier+INBOX@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=7069@debbugs.gnu.org \
--cc=dan.colascione@gmail.com \
--cc=hamren@sdu.se \
/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).