Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: Paul Grayson <pgrayson+ding@ks.uiuc.edu>, ding@gnus.org
Subject: Re: can back end keep track of *all* group info?
Date: Sat, 22 Dec 2001 23:32:56 +0100	[thread overview]
Message-ID: <ilu7kreopgn.fsf@extundo.com> (raw)
In-Reply-To: <vafelln55ol.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Sat, 22 Dec 2001 22:02:50 +0100")

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> I think if you just change the code for the %y spec in
> gnus-group-line-format to see if the backend has told you the right
> number and to use that number in lieu of the current estimate based
> on min and max article number, then you should be fine.

Yes.  I don't think this is very difficult.

> Alas, I don't know what exactly is that mechanism which allows the
> backend to report the %y number directly.  Simon?  I think you were
> the one telling me this.

I think I was thinking of nnchoke-request-group, but that isn't really
called until the group is entered.  Hm.  Could we extend
nnchoke-request-list perhaps?  If the backend knows the total number
of articles in the group it can report it.  It should be a optional
parameter.




  reply	other threads:[~2001-12-22 22:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-22  5:50 Paul Grayson
2001-12-22 12:20 ` Simon Josefsson
2001-12-24 18:57   ` Paul Grayson
2001-12-24 22:51     ` Simon Josefsson
2001-12-26 16:54       ` Paul Grayson
2001-12-26 18:17         ` Simon Josefsson
2001-12-22 21:02 ` Kai Großjohann
2001-12-22 22:32   ` Simon Josefsson [this message]
2001-12-23 10:19     ` Kai Großjohann
2001-12-23 22:18     ` Paul Jarc
2001-12-23 22:25 ` Paul Jarc

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ilu7kreopgn.fsf@extundo.com \
    --to=jas@extundo.com \
    --cc=ding@gnus.org \
    --cc=pgrayson+ding@ks.uiuc.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).