Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: all nnimap flags lost again
Date: Thu, 23 Sep 2010 03:10:38 +0200	[thread overview]
Message-ID: <m3sk11gt81.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87y6atgthy.fsf@uwo.ca>

Dan Christensen <jdc@uwo.ca> writes:

> Then, after setting the `E' mark on about a hundred articles, I exited
> the group.  When I reentered, the marks were gone again!  So I set them
> again, exited and reentered, and then they were there.  I decide to quit
> gnus and emacs in case some data structure was corrupted.  When I
> restarted, the marks were gone again.

Cripes.

> Since this is repeatable, maybe we can debug it?  Here's my *imap log*
> from one of the times that it happened:
>
> 20:59:56 68 SELECT "generic"
> 20:59:56 69 UID FETCH 29:2328 (UID RFC822.SIZE BODYSTRUCTURE BODY.PEEK[HEADER.FIELDS (Subject From Date Message-Id References In-Reply-To Xref X-Spam-Status To Cc Keywords Newsgroups Subject)])
> 21:00:26 70 UID STORE 2173:2181,2183:2224,2226:2279,2281:2315,2317:2327 +FLAGS.SILENT (gnus-expire)
>
> A lot of the articles are set to expire.

It's setting the marks OK.  But I can't see from any of the excerpts
that it removes the marks from the servers?  There's no "-FLAGS.SILENT"
in your logs?  Then the flags are still on the IMAP server -- it's only
Gnus that's not discovering them correctly.

> I think I entered the group twice, and both times it was fine.
>
> 21:01:12 75 SELECT "generic"
> 21:01:12 76 UID FETCH 1:* FLAGS
>
> That's probably me hitting `M-g'.
>
> 21:01:13 77 SELECT "generic"
> 21:01:13 78 UID FETCH 29:2328 (UID RFC822.SIZE BODYSTRUCTURE BODY.PEEK[HEADER.FIELDS (Subject From Date Message-Id References In-Reply-To Xref X-Spam-Status To Cc Keywords Newsgroups Subject)])

So `M-g' doesn't even restore the marks now?

There must be a basic marks parsing problem now.  Can you send the
complete contents of the *nnimap ... * buffer after doing one `M-g' on
the group?

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen




  reply	other threads:[~2010-09-23  1:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-23  1:04 Dan Christensen
2010-09-23  1:10 ` Lars Magne Ingebrigtsen [this message]
2010-09-23  1:17   ` Lars Magne Ingebrigtsen
2010-09-23  1:17   ` Dan Christensen
2010-09-23  1:24     ` Lars Magne Ingebrigtsen
2010-09-23  2:15       ` Dan Christensen
2010-09-23 16:01         ` Lars Magne Ingebrigtsen
2010-09-23 18:41           ` Dan Christensen
2010-09-23 18:45             ` Lars Magne Ingebrigtsen
2010-09-23 18:57               ` Dan Christensen
2010-09-23 19:04                 ` Dan Christensen
2010-09-23 19:43                   ` Lars Magne Ingebrigtsen
2010-09-23 19:45                 ` Lars Magne Ingebrigtsen
2010-09-23 23:34                   ` Dan Christensen
2010-09-23 23:54                     ` Lars Magne Ingebrigtsen
2010-09-24 14:48                       ` Dan Christensen
2010-09-24 16:06                         ` 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=m3sk11gt81.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    --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).