kitty> Probably unrelated. I got a stack overflow error (no crash) kitty> when I ran compile in a directory with a lot of output from kitty> the compiler. I guess the font-lock regexp parsing of the kitty> compiler output crashes when the compilation buffer becomes kitty> huge. Do you know of anything that I can do to prevent this kitty> ? This was with XEmacs-21.4.10 on Linux/x86. I think this is commonly seen on small-stack machines even with not so huge output. The slow but safe solution is to do find out what your CFLAGS are and do rm regex.o; CFLAGS += " -DREGEX_MALLOC" make regex.o; make. I didn't find it all that terribly slow when I tried it, but YMMV. You could port Ben's hybrid (alloca small, malloc large) solution from 21.5. Or you could buy more memory and set stacksize infinite, and cross your fingers. Finally, you can turn off font-lock. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.