Gnus development mailing list
 help / color / mirror / Atom feed
From: Frank Schmitt <ich@frank-schmitt.net>
To: ding@gnus.org
Subject: nnimap unread count broken again
Date: Mon, 18 Oct 2010 12:05:06 +0200	[thread overview]
Message-ID: <87fww3yfxp.fsf@mid.gehheimdienst.de> (raw)

Hello,

After Lars's rewrite of nnimap the problem that reading IMAP messages from
several Gnus instances caused wrong unread counts was fixed. However,
now it is there again and even worse then with the pre-Lars-nnimap.

If I get a new message, read it in Gnus A, then hit g in Gnus B, the
message is still unread. Even if I enter the group, the message is shown
as unread (at this point the old nnimap got it right at least). The
only way to get correct unread state and ticks is saying M-g on all nnimap
groups.

I think this problem was mentioned in previous messages already, so
before I start git bisecting or something: Is it already worked on?
The server in question is a dovecot BTW.

-- 
Have you ever considered how much text can fit in eighty columns?  Given that a
signature typically contains up to four lines of text, this space allows you to
attach a tremendous amount of valuable information to your messages.  Seize the
opportunity and don't waste your signature on bullshit that nobody cares about.




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

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-18 10:05 Frank Schmitt [this message]
2010-10-18 10:36 ` Steinar Bang
2010-10-18 10:47   ` Frank Schmitt
2010-10-18 11:01     ` Steinar Bang
2010-10-18 16:42       ` Dave Goldberg
2010-10-18 19:55         ` Lars Magne Ingebrigtsen
2010-10-18 19:25 ` Lars Magne Ingebrigtsen
2010-10-18 19:57   ` Frank Schmitt
2010-10-18 20:01     ` Lars Magne Ingebrigtsen
2010-10-18 20:02       ` Lars Magne Ingebrigtsen
2010-10-18 20:13         ` Frank Schmitt
2010-10-18 21:02         ` Dave Goldberg
2010-10-21 11:20         ` James Cloos
2010-10-21 16:01           ` Lars Magne Ingebrigtsen

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=87fww3yfxp.fsf@mid.gehheimdienst.de \
    --to=ich@frank-schmitt.net \
    --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).