Re: can back end keep track of *all* group info?

[Simon Josefsson <jas@extundo.com>]

Paul Grayson <pgrayson+ding@ks.uiuc.edu> writes:

> Okay, I think that I'm starting to see what I need to do to trick gnus
> into working correctly with my server.  M-g now updates my groups
> quite well.  However, 'g' still displays only the groups with ticked
> articles, and never thinks any groups have unread articles.

If so, does your `nnchoke-retrieve-groups' really return correct
information?  Guns certainly should notice new unread articles.

> Is there an easy way to replace whatever 'g' uses currently with the
> M-g update?  I'd like it to only display the groups that have new
> messages, and I want 'n' at the end of one group to jump correctly to
> the next unread group, so changing %y (as Kai proposed) isn't going to
> be good enough, right?
>
> Is the only difference between M-g and whatever 'g' does to each group
> that -request-group is called with the 'dont-check' option in the
> latter?

Replacing `g' with `M-g' stuff becomes slow for most backends, so this
isn't a good solution.  Ideally the `g' stuff should use additional
information from backends which are able to provide it, for display in
the *Group* buffer.

`n' should work since Gnus over-estimates the number of unread
articles, it never under-estimates them.  Maybe this is related to the
problem above.