Re: *reproducible* lost marks with nnimap

[David Abrahams <dave@boost-consulting.com>]

Simon Josefsson <jas@extundo.com> writes:

> David Abrahams <dave@boost-consulting.com> writes:
>
>>> Remember, flags are not synchronized with the server until you do,
>>> and the 'q' has successfully exited the group.  
>>
>> I understand you're saying that's how it works, but:
>>
>>   1. From a usability standpoint, it's just crazy that messages I've
>>      read become unread when I ask the summary to update with `M-g'.
>>      What possible purpose could that serve?
>
> You can still press 'q' in the summary buffer to save your flag
> changes (including which articles you read).  

But it takes a long time to do that (possibly because I have a great
many messages in my INBOX?), and closes my summary buffer.  That's a
big interruption.

> Pressing M-g shouldn't change this.  This isn't nnimap specific, so
> changing this probably should be discussed by itself first.

Maybe so.  Be my guest, everyone! ;-)

>>   2. After the server times out and says goodbye, nnimap often fails
>>      to re-establish the connection until after *two* tries.  The
>>      result, apparently, is that even pressing `q' sometimes drops
>>      marks because flag synchronization fails and there's no retry.
>
> This sounds like a nnimap bug, and I see it too.  I think it only
> applies to non-native network connections (e.g., via tls, ssh etc).
> Fixing this problem might make you not perceive the first problem as a
> problem, so it is important.  It hasn't annoyed me enough to debug
> yet, if anyone else like to debug it, that would be good.

It has annoyed me enough, for a very long time, but I got lost in the
tangle of Gnus and ran out of time.

It didn't seem to happen when I used Gnus under XEmacs, FWIW.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com