From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: <ding@gnus.org>
Subject: Re: `new' indicator for nnimap groups?
Date: Thu, 02 Aug 2001 17:05:37 +0200 [thread overview]
Message-ID: <vaflml2zem6.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0108021540340.19820-100000@lie.extundo.com> (Simon Josefsson's message of "Thu, 2 Aug 2001 15:51:00 +0200 (CEST)")
On Thu, 2 Aug 2001, Simon Josefsson wrote:
> Hmm. Ah, yes, I meant the active range. If you only have the
> currently highest/lowest article number, and get an updated count of
> articles in the mailbox, how do you know which articles exists in
> the mailbox? So Gnus doesn't know which articles to request from
> the backend when entering the group, unless it knows the
> highest/lowest article number. But still, this decision could be
> delayed from `g' to when you actually enter the group to speed
> things up. The backend interface probably needs to change for this,
> though.
My suggest was to change the backend interface in such a way that some
backends report the number of unread messages _in addition to_ the
low/high numbers. The rest of Gnus can continue to use the low/high
numbers as before, only the `draw the group buffer' code uses the
number of unread messages (if available).
I fail to see how Gnus could work less well when it has more
information?
kai
--
~/.signature: No such file or directory
next prev parent reply other threads:[~2001-08-02 15:05 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-28 11:25 Kai Großjohann
2001-07-28 13:44 ` Simon Josefsson
2001-07-28 16:18 ` Kai Großjohann
2001-07-28 21:34 ` Amos Gouaux
2001-07-28 21:49 ` Karl Kleinpaste
2001-07-28 22:32 ` Kai Großjohann
2001-07-28 23:24 ` Simon Josefsson
2001-07-28 23:01 ` Simon Josefsson
2001-07-28 23:12 ` Kai Großjohann
2001-07-28 23:49 ` Simon Josefsson
2001-07-29 21:07 ` Kai Großjohann
2001-07-30 11:09 ` Simon Josefsson
2001-07-30 12:52 ` Kai Großjohann
2001-08-02 10:54 ` Simon Josefsson
2001-08-02 12:08 ` Kai Großjohann
2001-08-02 13:51 ` Simon Josefsson
2001-08-02 15:05 ` Kai Großjohann [this message]
2001-08-02 15:32 ` Simon Josefsson
2001-08-02 15:51 ` Kai Großjohann
2001-07-28 13:46 ` Amos Gouaux
2001-07-28 20:10 ` Nuutti Kotivuori
2001-08-05 13:15 ` Simon Josefsson
2001-08-05 16:59 ` Kai Großjohann
2001-08-05 20:31 ` Simon Josefsson
2001-08-11 17:01 ` Kai Großjohann
2001-08-11 23:00 ` Simon Josefsson
2001-08-12 16:59 ` Kai Großjohann
2001-08-12 17:41 ` Simon Josefsson
2001-08-12 18:03 ` Kai Großjohann
2001-08-17 20:34 ` Lars Magne Ingebrigtsen
2001-08-17 21:14 ` Simon Josefsson
2001-08-17 21:28 ` Lars Magne Ingebrigtsen
2001-08-17 22:01 ` Kai Großjohann
2001-08-17 22:23 ` Lars Magne Ingebrigtsen
2001-08-17 22:30 ` Paul Jarc
2001-08-17 22:35 ` Lars Magne Ingebrigtsen
2001-08-17 22:44 ` Paul Jarc
2001-08-17 22:46 ` Lars Magne Ingebrigtsen
2001-08-18 3:28 ` Paul Jarc
2001-08-18 8:46 ` Simon Josefsson
2001-08-19 3:32 ` Paul Jarc
2001-08-17 23:02 ` Kai Großjohann
2001-08-18 9:20 ` Simon Josefsson
2001-08-18 9:47 ` Lars Magne Ingebrigtsen
2001-08-27 16:59 ` Sudish Joseph
2001-08-27 17:46 ` Simon Josefsson
2001-08-28 0:21 ` Amos Gouaux
2001-08-28 0:28 ` Amos Gouaux
2001-08-17 23:00 ` Kai Großjohann
2001-08-17 23:02 ` Lars Magne Ingebrigtsen
2001-08-18 0:44 ` Joe Casadonte
2001-08-18 2:27 ` Paul Jarc
2001-08-18 11:44 ` Joe Casadonte
2001-08-18 9:04 ` Simon Josefsson
2001-08-27 16:47 ` Sudish Joseph
2001-08-18 0:41 ` Joe Casadonte
2001-08-18 15:34 ` Kai Großjohann
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=vaflml2zem6.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.org \
/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).