Re: font-lock and autoload is broken

Matt> I assume the patch to autoload.el is the one I suggested? Is Matt> it worth committing it until I can figure out why the Matt> behavior changed? Please commit that one, but don't stop looking for the cause. Matt> As for the new font-lock.el chewing up the CPU, I haven't Matt> been able to reproduce this. Could you possibly point me in Matt> the right direction? (Either send me your Matt> (describe-installation) output, or dump XEmacs while the CPU Matt> is hung and give me a stack backtrace; or both.) I'd like to Matt> get this fixed; I just need somewhere to start. Also try profiling it. It's likely that it's problem in the Lisp logic, and the stack backtrace won't help as much as a profile. See the recent thread on xemacs-beta between Ben and Chris Holt (on this topic!) for a quick howto (there's a pointer to the thread in http://www.xemacs.org/Releases/Public-21.2/tester.html). I don't think Ben's patch has been committed yet so that could be the problem. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."