Progress bars + events [Re: crash when using W3]
Ben Wing <ben(a)666.com> writes:
we wouldn't need to inhibit event processing. bill perry would
get a lisp
error upon buffer deletion, and would then have to change his code not to
trigger event processing in after-change.
We have a catch-22 here. The code is that is triggering the event processing
is to display progress bars and Andy's says event processing is NEEDED there
:-(
It doesn't even help to inhibit process events because for instance the GPM
code (text based mouse support) uses them.
May we should simply start by signalling an error and see what breaks..
Jan