Gnus development mailing list
 help / color / mirror / Atom feed
From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: all nnimap flags lost again
Date: Wed, 22 Sep 2010 22:15:26 -0400	[thread overview]
Message-ID: <87iq1xi4sh.fsf@uwo.ca> (raw)
In-Reply-To: <m3y6atdzfs.fsf@quimbies.gnus.org>

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Dan Christensen <jdc@uwo.ca> writes:
>
>> Can you increase the size of that buffer, as it often doesn't contain
>> the results from a single action?  
>
> 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.

Before I did the `M-g', the buffer showed the response to command 181,
so I thought 182 was missing.  And 181 certainly went missing.  So
old stuff definitely disappears from that buffer, making it hard to
see what happened a few minutes ago.

> Anyway, everything looks OK in the buffer, and the fix I just pushed
> should fix the problem if you `M-g' the affected groups.

It seems to have worked, although somehow in the process some of the
! and ? marks really did lost.  Oh, well.

I wrote:

> Also, I don't know if it's related, but when I hit SPC on an nnimap
> group right after starting Gnus, it only shows me the articles whose
> numbers are within 100 of the most recent.  I was hoping that the trick
> of just looking at the last 100 would be completely internal.

I guess that was unrelated, but it is happening.

Dan




  reply	other threads:[~2010-09-23  2:15 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   ` 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 [this message]
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=87iq1xi4sh.fsf@uwo.ca \
    --to=jdc@uwo.ca \
    --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).