Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Returning to ticks on read-only imap servers
Date: Fri, 08 Oct 2010 20:49:40 +0200	[thread overview]
Message-ID: <m3lj68jz97.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87vd5czggz.fsf@keller.adm.naquadah.org>

Julien Danjou <julien@danjou.info> writes:

> No, it gives you if the box changed, and how many messages/unread it
> has. That looks like enough info to print the group buffer. Or not?

Not.  :-)  You only know the number, not which ones, so you can't really
say what happened.

If you had high 50, unseen 25, and it increase to high 55, unseen 23,
how do you know whether that's 5 new articles, and two old that were
read, or 1 new article, and three that were read?

Just work through the scenarios, and keep in mind that the UIDNEXT isn't
necessarily consecutive. 

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen




  reply	other threads:[~2010-10-08 18:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05 19:16 Michael Welsh Duggan
2010-10-05 20:25 ` Steinar Bang
2010-10-05 21:01   ` Michael Welsh Duggan
2010-10-07 18:59 ` Lars Magne Ingebrigtsen
2010-10-07 21:37   ` Michael Welsh Duggan
2010-10-07 22:40     ` Lars Magne Ingebrigtsen
2010-10-08 15:07       ` James Cloos
2010-10-08 17:00         ` Lars Magne Ingebrigtsen
2010-10-08 18:22           ` Julien Danjou
2010-10-08 18:26             ` Lars Magne Ingebrigtsen
2010-10-08 18:28               ` Julien Danjou
2010-10-08 18:49                 ` Lars Magne Ingebrigtsen [this message]
2010-10-08 19:34                   ` Julien Danjou
2010-10-08 21:32                     ` Dan Christensen
2010-10-09  6:57                       ` Julien Danjou
2010-10-09  8:10                         ` Michael Welsh Duggan
2010-10-09  8:26                           ` Julien Danjou

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=m3lj68jz97.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    --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).