Gnus development mailing list
 help / color / mirror / Atom feed
From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: gnus and imap
Date: Mon, 07 Dec 2009 13:57:36 -0500	[thread overview]
Message-ID: <87ws0yipcv.fsf@uwo.ca> (raw)
In-Reply-To: <87r67d3jp9.fsf@randomsample.de>

In 2008, regarding Vitaly Mayatskikh's patches, David Engster writes:

> I've finally come to test your patches. Sorry for the delay.
>
> I'm still sometimes encountering wrong article counts upon entering a
> group. This happens when I delete articles in a group and enter it
> without a rescan. The group will then show an unread count which is
> usually equal to the number of deleted articles. This gets reset to zero
> when you exit the group, so you can only see that with a three-pane
> view, where the group buffer is always visible.
>
> However, this is only indirectly a consequence of your patches. The
> problem seems to be that when you delete some articles in a group, the
> active information does not get updated in the hash table, so that
> (gnus-range-difference active range) will return a range containing the
> deleted articles.
>
> This is all fixable, of course. However, before continuing with this
> approach, I'd still like to suggest using a new backend function instead
> of storing the number of available articles numbers in the
> active-hashtb. The latter implies that we would have to check the whole
> Gnus trunk for regressions regarding usage of the active-hashtb, which
> will be a lot of work. I think that using something like
> nnimap-request-group-articles and leaving the active-hashtb as it is
> would be easier to do in the long term. If you (or others) don't object,
> I could try to change your patches using that new backend function.
>
> Best,
> David

I'm wondering if Vitaly or David have made any progress on the imap
unread count.  I'm using dovecot, and I regularly get wrong unread
counts in my nnimap groups, even with
gnus-fixup-nnimap-unread-after-getting-new-news in
gnus-after-getting-new-news-hook.

I think David's idea of adding an optional backend function which
returns more detailed information is the way to go.  The core of Gnus
can check for this function and use it if it exists, falling back to the
old way if not.  This allows for a gradual transition without needing
massive changes all at once.

Dan




  reply	other threads:[~2009-12-07 18:57 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19 16:14 Vitaly Mayatskikh
2008-08-19 20:12 ` Frank Schmitt
2008-08-19 22:24   ` Vitaly Mayatskikh
2008-08-20  6:42     ` Vegard Vesterheim
2008-08-20  7:41       ` Vitaly Mayatskikh
2008-08-20 16:16 ` David Engster
2008-08-21  6:26   ` Vitaly Mayatskikh
2008-08-21 11:27     ` David Engster
2008-08-21 12:57       ` Tibor Simko
2008-08-22  8:44         ` Vitaly Mayatskikh
2008-08-22  8:54           ` David Engster
2008-08-22 15:35           ` Tibor Simko
2008-08-21 15:06       ` Vitaly Mayatskikh
2008-08-21 21:15       ` Frank Schmitt
2008-08-22 12:13       ` Reiner Steib
2008-08-22 12:30         ` Vitaly Mayatskikh
2008-08-22 15:50           ` Ted Zlatanov
2008-08-22 16:10             ` Vitaly Mayatskikh
2008-08-22 16:21         ` David Engster
2008-08-22 16:27           ` Vitaly Mayatskikh
2008-08-22 17:33             ` David Engster
2008-08-22 18:11               ` Vitaly Mayatskikh
2008-08-23  9:19                 ` David Engster
2008-08-23 11:32                   ` Vitaly Mayatskikh
2008-08-23 14:52                     ` David Engster
2008-08-24  8:47                       ` Vitaly Mayatskikh
2008-08-24 18:09                         ` David Engster
2008-08-24 19:29                           ` Reiner Steib
2008-08-24 23:39                             ` David Engster
2008-08-25 19:22                               ` James Cloos
2008-08-25  0:00                           ` Daniel Pittman
2008-08-25  9:46                             ` David Engster
2008-08-25 18:02                               ` Ted Zlatanov
2008-08-25 19:50                                 ` David Engster
2008-08-25  8:05                           ` Vitaly Mayatskikh
2008-08-25 12:25                             ` David Engster
2008-08-25 13:17                               ` Vitaly Mayatskikh
2008-08-25 17:53                         ` Ted Zlatanov
2008-08-24  9:18                       ` Vitaly Mayatskikh
2008-08-24 10:08                         ` David Engster
2008-08-26 20:40                           ` Vitaly Mayatskikh
2008-09-03 11:55                             ` David Engster
2008-09-21  9:57                               ` David Engster
2009-12-07 18:57                                 ` Dan Christensen [this message]
2009-12-10 20:08                                   ` Dan Christensen
2009-12-11 20:36                                     ` David Engster
  -- strict thread matches above, loose matches on Subject: below --
2002-07-09  8:52 gnus and IMAP me
2002-07-09  9:29 ` Niklas Morberg
2002-07-09 10:17   ` me
2002-07-09 10:27   ` me
2002-07-09 10:52   ` me

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=87ws0yipcv.fsf@uwo.ca \
    --to=jdc@uwo.ca \
    --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).