Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Dave Abrahams <dave@boostpro.com>
Cc: ding@gnus.org,  John Wiegley <johnw@boostpro.com>
Subject: Re: Updated IMAP unread count correction
Date: Mon, 11 Jun 2012 00:12:58 +0200	[thread overview]
Message-ID: <m3bokqdded.fsf@stories.gnus.org> (raw)
In-Reply-To: <m28vfuq0y4.fsf@pluto.luannocracy.com> (Dave Abrahams's message of "Sun, 10 Jun 2012 18:03:31 -0400")

Dave Abrahams <dave@boostpro.com> writes:

> It won't do any good at all to run that code unless I can get it to
> report the right number, so that I'll notice when it reports the wrong
> one.  If you can tell me how to get things back in sync, I can try
> running the normal code again.  

(gnus-clean-old-newsrc t) and then `g'.

> [Incidentally, one thing I dearly wish for in Gnus is the ability to say
> "throw out all the information you have that can be derived from the
> server (and re-derive it on demand)."

`M-g' on each group will do that.

> I don't know if it helps, but I am using a local dovecot with
> offlineimap and recently had to rebuild the local mailstore.  Thus the
> UIDs of messages on the server could easily have been changed.

Gnus should detect that and do a full rescan.  Unless the IMAP server
doesn't change its UIDVALIDITY...

>> `G E' on a group will show you what messages Gnus thinks don't exist on
>> the server.  (In the `unexist' list.)  If that gets out of sync,
>> something wrong happened.
>
> `G E' on my INBOX currently shows more than 800 "seen" entries and about
> 3 in the unexist list.  There are only 3 messages actually existing in
> that mailbox.  Not sure what that tells you, though.

It tells me that your .newsrc.eld data is messed up.  :-) But not much
more.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/



  reply	other threads:[~2012-06-10 22:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-01 21:08 Dave Abrahams
2012-06-10 19:36 ` Lars Magne Ingebrigtsen
2012-06-10 21:07   ` Dave Abrahams
2012-06-10 21:13     ` Lars Magne Ingebrigtsen
2012-06-10 21:25       ` Dave Abrahams
2012-06-10 21:39         ` Lars Magne Ingebrigtsen
2012-06-10 22:03           ` Dave Abrahams
2012-06-10 22:12             ` Lars Magne Ingebrigtsen [this message]
2012-06-11 14:53               ` Julien Cubizolles
2012-09-05 14:04                 ` Lars Ingebrigtsen
2012-06-12 14:29               ` Dave Abrahams
2012-09-05 14:05                 ` Lars Ingebrigtsen
2012-09-05 17:20                 ` Dave Abrahams
2012-09-05 17:56                   ` Lars Ingebrigtsen
2012-09-05 19:41                     ` Dave Abrahams
2012-09-05 19:46                       ` Lars Ingebrigtsen
2012-09-05 20:01                         ` Dave Abrahams
2012-09-17 19:06                           ` Dave Abrahams
2012-12-25 12:24                             ` Lars Ingebrigtsen
2012-07-11 13:25         ` Myles

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=m3bokqdded.fsf@stories.gnus.org \
    --to=larsi@gnus.org \
    --cc=dave@boostpro.com \
    --cc=ding@gnus.org \
    --cc=johnw@boostpro.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).