On Fri, 3 Sep 2010 18:30:04 +0100
Glynn Clements <glynn(a)gclements.plus.com> wrote:
The problem still exists in 21.4.22. I find that it happens for any
sufficiently large compilation buffer. A sample compilation buffer and
the associated backtrace from next-error are attached.
Thanks, I was able to reproduce it. But only with -vanilla, with my
"normal" setup it worked fine. This was expected since kernel compile
outputs are huge and have never caused me a problem.
So there is a workaround.... it seems the following line in my init.el
fixes the problem:
(setq compilation-error-regexp-systems-list '(gnu))
This limits the regular expressions used for matching and is a huge
performance gain if you only use the gnu compiler. Note: You might
want to also optimize for perl and/or python if you use those languages
a lot.
In your case it looks like the comma and cray entries cause problems.
The following works for me with your compilation buffer:
(setq compilation-error-regexp-systems-list
'(
4bsd
ada
aix
ant
borland
caml
;; comma
;; cray
epc
gnu
iar
ibm
lcc
mips
msft
of
oracle
perl
python
xerces-j
rxp
sgi
sgimipspro
sun
ultrix
))
(compilation-build-compilation-error-regexp-alist)
I haven't looked into why those regular expressions are a problem.
Cheers,
Sean
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/mailman/listinfo/xemacs-beta