Andy Piper wrote:
At 11:19 PM 4/27/00 -0700, Ben Wing wrote:
>andy, did you miss this comment in lazy-lock?
This was not the case I was referring to. Evidently lazy-lock is more
broken than I thought. You need to try Martin's "gutter flicker" test to
really see lazy-lock chew CPU cycles. In this scenario set-buffer gets
called almost contiuously which, from my brief look, will modify
frame-modified-tick.
andy, there's something you're just not getting: blaming packages because they
do something that tickles a gutter bug is just not kosher. your mindset needs
to shift from "other packages can't do this or that or the other thing too
frequently" to "the gutter code needs to be robust enough that other packages
can do what they want". everything else in xemacs works this way. if the
gutter code is going to remain in xemacs, it needs to work this way too.
*everyone* calls set-buffer. this is a totally standard function.
Anyway, I'm glad you fixed the problem you were seeing. Thanks.
andy
--------------------------------------------------------------
Dr Andy Piper
Principal Consultant, BEA Systems Ltd
--
Ben
In order to save my hands, I am cutting back on my mail. I also write
as succinctly as possible -- please don't be offended. If you send me
mail, you _will_ get a response, but please be patient, especially for
XEmacs-related mail. If you need an immediate response and it is not
apparent in your message, please say so. Thanks for your understanding.
See also
http://www.666.com/ben/chronic-pain/