From: David Abrahams <dave@boost-consulting.com>
Subject: Re: *reproducible* lost marks with nnimap
Date: Tue, 13 Jan 2004 10:17:06 -0500 [thread overview]
Message-ID: <uhdyzswst.fsf@boost-consulting.com> (raw)
In-Reply-To: <ilu65fgsph2.fsf@latte.josefsson.org> (Simon Josefsson's message of "Tue, 13 Jan 2004 00:43:05 +0100")
Simon Josefsson <jas@extundo.com> writes:
> David Abrahams <dave@boost-consulting.com> writes:
>
>> I figured out how to reproduce the "nnimap lost marks" problem:
>>
>> 1. visit the *Summary INBOX* buffer
>> 2. read a few mails so they are marked `expired'
>> 3. *wait* for the IMAP server to get bored and close the connection.
>> 4. Hit `M-g' in the summary buffer to get new mail
>>
>> Note that the mails you previously read will be marked unread again.
>
> Did you type 'q' in the *Summary* buffer?
No.
> 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?
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.
> You can press 'Q', or simply C-k a summary buffer, and any flag
> changes you made (except explicit delete) will be lost. So
> prematurely sending the flag updates is not right.
Then you should consider sending them when `M-g' is done.
--
Dave Abrahams
Boost Consulting
www.boost-consulting.com
next prev parent reply other threads:[~2004-01-13 15:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 22:30 David Abrahams
2004-01-12 23:43 ` Simon Josefsson
2004-01-13 15:17 ` David Abrahams [this message]
2004-01-13 23:23 ` Simon Josefsson
2004-01-13 23:27 ` David Abrahams
2004-01-13 23:27 ` David Abrahams
2004-01-15 9:38 ` Kai Grossjohann
2004-01-15 10:27 ` Simon Josefsson
2004-01-15 11:36 ` Kai Grossjohann
2004-01-15 13:43 ` Simon Josefsson
2004-01-15 15:48 ` Chris Shenton
2004-01-15 18:11 ` Simon Josefsson
2004-01-16 17:42 ` Chris Shenton
2004-01-17 2:33 ` Simon Josefsson
2004-01-15 21:06 ` David Abrahams
2004-01-16 5:36 ` Kevin Greiner
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=uhdyzswst.fsf@boost-consulting.com \
--to=dave@boost-consulting.com \
/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).