From: Frank Schmitt <ich@frank-schmitt.net>
To: ding@gnus.org
Subject: IMAP unread count
Date: Tue, 21 Apr 2009 09:50:56 +0200 [thread overview]
Message-ID: <m3zlea1m3j.fsf@mid.gehheimdienst.de> (raw)
Hello,
Say I start Gnus on machine A, read mails in IMAP folder INBOX until
mail number 42. Then I start Gnus in machine B and catchup in the same
IMAP folder so both have the same unread status. Then mail 43 arrives, I
read it in the Gnus on machine B, so there unread count is 0. When I say
g in summary buffer of machine A, I still get an unread count of 1.
I had the impression there was a patch for this long standing (and
irritating) bug. Am I mistaken or wasn't it incorporated or is my Gnus
too old?
Frank
--
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.
next reply other threads:[~2009-04-21 7:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 7:50 Frank Schmitt [this message]
2009-04-23 14:34 ` Frank Schmitt
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=m3zlea1m3j.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).