Re: What's the problem?

[Eli Zaretskii]

> From: Simon Josefsson <address@hidden>
> Date: Wed, 10 Dec 2003 07:34:45 +0100
> >
> > What I'm trying to say is that the `threading support' need not be
> > particularly good, or general-purpose.  Probably something could be
> > hacked up right _now_, without any additional core functions, using
> > clever programming and emacs timers, by changing the worst-offending
> > part of the gnus code into something event driven.
> 
> I don't understand.  How would making the summary buffer generation
> asynchronous stop Emacs from locking up during computations?  For me,
> the summary buffer generation is CPU bound in elisp, not IO bound.

By doing the computation in chunks, like stealth font-lock does, for
example, you let other tasks get slots of CPU time while the long
computation runs.

It's like telling the user to go for a coffee while Gnus computes the
summary buffer, only instead of coffee she can type away something in
another buffer ;-)