Re: Oort Gnus

[Big Gaute <gs234@cam.ac.uk>]

Harry Putnam <reader@newsguy.com> writes:

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> 
> > "Johan Kullstam" <kullstam@ne.mediaone.net> writes:
> > 
> > > btw what wants to be done in the new gnus?  is there a wish-list of
> > > sorts somewhere?
> > 
> > There was a discussion on this list a while ago.  Not many features
> > were requested, I recall.
> 
> 
> Agent ... Agent and more Agent.
> 
> Agent functions need to be brought into line with the full scope of
> mail backend options.   Full manipulation of agent files as if gnus
> owned them (which it does )

Speaking as a fairly new gnus user, I can only agree.  I used agent
and imap at home this Christmas to read my mail (including several
mailing lists) and it worked quite well, but it is all a bit crude.
It would be nice if agent was smart enough to always store articles
that I read while plugged, and only use the plugged / unplugged status
to decide whether to go and look at the server as well as among
locally stored articles.

A somewhat related thing I'd like to see would be a divorce between
some of the more specialised backends, in particular nndraft, and the
actual backend used to store the articles.  Possibly agent could be
implemented as a sort of middleman in such a layer, though I wouldn't
know.

It's a bit rude of me to suggest sweeping changes like this without
any real knowledge of what goes on inside gnus, but at least I think
it should be clear what sort of functionally I'm missing.

-- 
Big Gaute (not to be confused with LG)
"There was a time when a guy who died at forty was revered as the toughest
and most doggedly ancient son of a bitch in Cow Ass Clearing, Shitoleshire,
Engalond, back in the year dot." - Spider Jerusalem, Transmetropolitan #25