Re: font-lock-after-change function unbearably slow; Ben change?
Ben Wing writes:
ok i understand what's going on. i need to rewrite the font-lock
after-change functions to use text properties instead of extents, and add
some additional trickiness for deletes. as it is, you're getting 7900
extents in the buffer generated by 7900 text-insertion operations, and
each insertion operation needs to adjust the endpoint of all following
extents ... you get the N^2 idea.
Just like Newton's apple: It fell right on my head. :-)
i'll fix this within a couple of days and send a patch.
Sweet. Thanks.
thanks once again for the investigative work, chris.
Most welcome, but I must admit that I'm one of those that needs font-lock to
work. I don't use the menubar, speedbar, buffers-tab, or gutter, but I *do*
worship at the altar of font-lock... and dynamic completion. Best things for
programming since the invention of the compiler.
Chris