From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: all nnimap flags lost again
Date: Thu, 23 Sep 2010 03:24:39 +0200 [thread overview]
Message-ID: <m3y6atdzfs.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <871v8lcl77.fsf@uwo.ca>
Dan Christensen <jdc@uwo.ca> writes:
>> 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?
>
> Can you increase the size of that buffer, as it often doesn't contain
> the results from a single action? I switched groups here to another
> one "root" which shows the same problem, and just a bit at the beginning
> is truncated.
The buffer shouldn't be truncated -- a `M-g' just issues a SELECT and a
FETCH FLAGS:
> * FLAGS (%Answered %Flagged %Deleted %Seen %Draft gnus-expire gnus-dormant)
> * OK [PERMANENTFLAGS (%Answered %Flagged %Deleted %Seen %Draft gnus-expire gnus-dormant %*)] Flags permitted.
> * 113 EXISTS
> * 0 RECENT
> * OK [UIDVALIDITY 1256067223] UIDs valid
> * OK [UIDNEXT 1799] Predicted next UID
> 183 OK [READ-WRITE] Select completed.
> * 1 FETCH (UID 757 FLAGS (%Seen))
[...]
> * 112 FETCH (UID 1797 FLAGS (%Seen gnus-expire))
> * 113 FETCH (UID 1798 FLAGS (%Seen gnus-expire))
> 184 OK Fetch completed.
And that looks like the complete response from the SELECT and the
FLAGS. The IMAP response protocol is slightly unusual -- it first
issues a lot of data on lines that start with "*", and then the numbered
response line ends the response, instead of the other way around, which
is how most other protocols do it. I think the IMAP way makes more
sense -- you don't have to add an explicit end-of-response line, since
the numbered status line ends the response.
Anyway, everything looks OK in the buffer, and the fix I just pushed
should fix the problem if you `M-g' the affected groups.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-09-23 1:24 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
2010-09-23 1:17 ` Dan Christensen
2010-09-23 1:24 ` Lars Magne Ingebrigtsen [this message]
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
2010-09-23 1:17 ` 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=m3y6atdzfs.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).