Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: bug in gnus-fixup-nnimap-unread-after-getting-new-news?
Date: Sat, 24 May 2003 12:42:19 +0200	[thread overview]
Message-ID: <iluptm84odw.fsf@latte-wlan.josefsson.org> (raw)
In-Reply-To: <4nllwxsg1j.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Fri, 23 May 2003 13:56:24 -0400")

Ted Zlatanov <tzz@lifelogs.com> writes:

> When the function gnus-fixup-nnimap-unread-after-getting-new-news gets
> run by the gnus-after-getting-new-news-hook, the unread counts are
> wrong for me.  For instance, "spam" (nnml backend) will get the same
> amount of unread messages as "nnimap+mail.lifelogs.com:mail" (nnimap
> backend).  Looking at the
> gnus-fixup-nnimap-unread-after-getting-new-news function, it appears
> to me that it uses the mailbox name as known to nnimap internally,
> which would only be correct if the nnimap server was the primary
> server.
>
> Furthermore, the function seems to use nnimap-mailbox-info, which is
> applicable only to the current IMAP server, so probably there will be
> issues with multiple IMAP servers as well.  Please let me know if I'm
> mistaken about this, so I can look elsewhere.

I think you are right.  Maybe it is time to implement Kai's suggestion
of a new backend API to support this function properly?




  reply	other threads:[~2003-05-24 10:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-23 17:56 Ted Zlatanov
2003-05-24 10:42 ` Simon Josefsson [this message]
2003-05-24 11:04   ` Ted Zlatanov
2003-05-24 14:13     ` Simon Josefsson
2003-05-25 10:56       ` Ted Zlatanov
2003-05-27 17:24         ` Ted Zlatanov
2003-05-27 22:05           ` Simon Josefsson
2003-05-29 14:54             ` Ted Zlatanov
2003-05-29 16:27               ` Simon Josefsson
2003-05-30 22:15                 ` Ted Zlatanov
2003-05-31  3:54                   ` Simon Josefsson
2003-05-31 11:37                     ` Ted Zlatanov

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=iluptm84odw.fsf@latte-wlan.josefsson.org \
    --to=jas@extundo.com \
    /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).