Re: font-lock-after-change function unbearably slow; Ben change?
"Stephen J. Turnbull" wrote:
>>>>> "Ben" == Ben Wing <ben(a)666.com> writes:
Ben> indeed i did change this and i can't see why those calls to
Ben> make-extent should have such a slowdown effect.
I was afraid of that.
Ben> [b] someone broke the redisplay extent optimization code.
Can you give me some function names or other ways to localize
dangerous changes for `cvs annotate'? I consider this a priority item
for the release. Slow font-lock sucks badly for too many people.
well, the extent_changed_for_redisplay() function and the extents_changed flag,
but that's imho not likely to yield anything.
best to start with chris's case and investigate closely what's causing the
slowdown.
Ben> but even more to the point, redisplay should not even be
Ben> getting called at all.
The only thing I can think of off-hand is that Andy has done several
"set-yet-another-dirty-flag" fixes for the widget code. Andy?
Chris, do you have the progress bar enabled? It may not matter if
it's invisible, depending on where those flags are getting set. (NB:
Matt Tucker's password buffer bug is a background font-lock 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."
--
ben
I'm sometimes slow in getting around to reading my mail, so if you
want to reach me faster, call 520-661-6661.
See http://www.666.com/ben/chronic-pain/ for the hell I've been
through.