None
Andy Piper writes:
At 02:58 AM 3/15/00 -0700, Ben Wing wrote:
>interesting is that while lazy-lock is doing its thing, it does a
>select-window, which calls record-buffer, which runs some hook (clearly
>an Andy hook).
The buffer recording in lazy-lock is erronous. I didn't fix it because
I fixed the root behaviour (tab flashing) and because I thought lazy-lock
was evil. The select-window really should have recording switched off
because it is called half a zillion times and the window selected is
restored anyway.
Grimly I point out that if we ignored recording changes until
redisplay was called and then compared old state to new state it
would make little difference what lazy-lock did. Existing code
is written expecting the redisplay to work this way. You have a
long battle ahead if you're going to fix all the code that makes
this assumption.