Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Performance problem of imap move
Date: Tue, 27 Jan 2015 11:46:11 +0800	[thread overview]
Message-ID: <87oapkrim4.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87siex213n.fsf@gnu.org>

Tassilo Horn <tsdh@gnu.org> writes:

> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>>> This will have to be refactored a bit, and a new nnimap function will
>>> have to be written, I think...
>>
>> I've now done this, so moving IMAP messages to large groups should be
>> faster again.
>
> I don't know if that's a side-effect of this change but with today's
> Gnus version I sometimes get group lines like
>
>     38289: nnimap+Server:some.group
>
> where actually there are no unread articles in the group.  `M-g' on the
> group or another `g' fixes the unread count again.
>
> I also don't have a reproducible recipe but it seems to happen
> sporadically with random nnimap groups.  Not sure what I did before.
> Possibly, it happens when some.group is either my sent-mail or SPAM
> group, and previously I've sent a new mail or exited some other group
> where I've marked some messages as SPAM which are moved to my SPAM group
> as a result...
>
> Bye,
> Tassilo

I see something like this (and have for a very long time, this isn't
new) when moving messages between nnimap groups. When I open an imap
group containing new messages, and decide that one of the
(newly-received but now marked "read") messages belongs in a different
group on the same server, I move it to that group, return to the *Group*
buffer, and see that the group I moved the message to now has an
(apparently random) unread count. Hitting "g" or actually entering the
group makes the unread count go away -- the messages aren't actually
marked as unread.

Might be unrelated, though: as I said, it's done this (fairly
reproducibly) for a long time.




  parent reply	other threads:[~2015-01-27  3:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 19:06 Mickaël Rémond
2015-01-21 14:11 ` Mickaël Rémond
2015-01-25  4:57   ` Lars Ingebrigtsen
2015-01-26  2:52     ` Lars Ingebrigtsen
2015-01-26 12:11       ` Tassilo Horn
2015-01-26 16:55         ` Steinar Bang
2015-01-27  0:54         ` Lars Ingebrigtsen
2015-01-27  7:23           ` Tassilo Horn
2015-01-27  7:28             ` Tassilo Horn
2015-01-27  7:30             ` Lars Ingebrigtsen
2015-01-27  8:01               ` Tassilo Horn
2015-01-27  8:05                 ` Tassilo Horn
2015-01-28  0:45                   ` Lars Ingebrigtsen
2015-01-27  3:46         ` Eric Abrahamsen [this message]
2015-01-27  4:48           ` Lars Ingebrigtsen
2015-01-27  5:02             ` Eric Abrahamsen
2015-01-27  5:09               ` Lars Ingebrigtsen
2015-01-27 14:41                 ` Steinar Bang
2015-01-28  2:06                   ` Dave Goldberg
2015-01-29  5:11                     ` Dave Goldberg
2015-01-28  2:29                 ` Eric Abrahamsen
2015-01-28  4:08                   ` Eric Abrahamsen
2015-01-28  4:10                     ` Eric Abrahamsen
2015-01-28  4:32                       ` Eric Abrahamsen
2015-01-28  5:08                         ` Lars Ingebrigtsen
2015-01-28  5:13                           ` Lars Ingebrigtsen
2015-01-28  5:52                             ` Eric Abrahamsen
2015-01-28 14:22                             ` Tassilo Horn
2015-01-29  1:08                               ` Lars 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=87oapkrim4.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.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).