Re: font-lock and autoload is broken
-- Steve Youngs <youngs(a)xemacs.org> spake thusly:
Currently, I have to use an old version of font-lock.el and a
locally
patched version of autoload.el just to get through my day.
Without the old font-lock.el XEmacs just sits there eating up the CPU
whenever it tries to fontify anything. It doesn't crash, but nothing
can be done until after repeated C-g's.
And I can't build the packages with the current autoload.el. I get an
"Unbalanced Parentheses" error when trying to create auto-autoloads.
I'm pretty sure that both of these things are related to Matt Tucker's
recent syntax-table tom-foolery (no offense Matt, I'm angry at my
computer, not you).
Matt, could you please, please fix this.
I'll certainly try.
I assume the patch to autoload.el is the one I suggested? Is it worth
committing it until I can figure out why the behavior changed? I
haven't really had time to look at it, as I've been working on cleaning
up issues involving mule and high-bit characters.
As for the new font-lock.el chewing up the CPU, I haven't been able to
reproduce this. Could you possibly point me in the right direction?
(Either send me your (describe-installation) output, or dump XEmacs
while the CPU is hung and give me a stack backtrace; or both.) I'd like
to get this fixed; I just need somewhere to start.