Re: gutter garbage insanity
At 09:57 PM 4/26/00 -0700, Ben Wing wrote:
andy, puhleeeze!
"turn off lazy lock" is not the solution. the solution is to fix the gutter
code to avoid recalculation!
You didn't answer my question and I didn't suggest that was the solution. I
still want to know if turning off lazy lock cures this for you.
I suspect that it does. This is because if you step through the lazy-lock
code you will see that it sits in an endless cycle - while idle! - setting
the window buffer to different things. The garbage you see is not the
gutter getting recalculated - it is the gutter constantly checking whether
anything has changed. I don't believe frame modified tick will help since
the frame *has* been modified.
it shouldn't matter what other lisp packages do.
This is clearly not true. It is always possible to write bad lisp packages
that consume CPU / memory / whatever. I believe that lazy-lock is such a
package.
if the gutter code isn't made robust enough by release time,
we'll have to
disable it by default.
If you are basing this on quality of implementation then lazy-lock should
have got shot in the head long ago.
andy
--------------------------------------------------------------
Dr Andy Piper
Principal Consultant, BEA Systems Ltd