Re: Gnus vs Wanderlust

[Miles Bader <miles@gnu.org>]

colin.rafferty@morganstanley.com writes:
> 1. It does not cache summary layout information.  When it builds a
>    summary, it has to start from scratch.

Is this actually a problem?  Judging from what I see, the great bulk of
the time is _not_ in summary generation, but rather getting info from
the server (which is where the sparse-range problems show up too).

[My computer's pretty slow by contemporary standards too -- a 450MHz
pentium]

I suppose one could try to cache and incrementally update summaries, but
summary-generation is already so fast, even for very large groups, that
it might make more sense to investigate whether it could be made even
faster (maybe even with some new emacs primitives).

Having `in between' summary generation might be nice too, especially
when just updating a summary buffer with M-g -- for instance, delete and
regenerate all threads where anything changed (message disappeared,
message added ...) would probably be very fast, as in a large group,
this would avoid regenerating most of the summary.

-Miles
-- 
Next to fried food, the South has suffered most from oratory.
  			-- Walter Hines Page