From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: fast list
Date: Tue, 19 Oct 2010 07:58:08 +0200 [thread overview]
Message-ID: <87zkua3erz.fsf@dod.no> (raw)
In-Reply-To: <m3r5fn8b8r.fsf@quimbies.gnus.org>
>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org>:
> Returning the FLAGS for all the groups will be so much data that's
> it's not generally useful. However, a global QRESYNC would be
> excellent. QRESYNC works by outputting all the flags that have
> changed since <SEQUENCE>. So if you said
That's why you need to M-g to sync up nnimap groups in different,
.newsrc.eld, so that they would have the right <SEQUENCE>?
But... if you read something on one gnus, and then go to a different
gnus, won't that different gnus have its old <SEQUENCE> and thus show
unread articles on the group(s)?
Obviously something I don't understand, because it does seem to
work... at least most of the time...:-)
next prev parent reply other threads:[~2010-10-19 5:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 5:15 James Cloos
2010-10-17 22:02 ` Lars Magne Ingebrigtsen
2010-10-17 22:58 ` James Cloos
2010-10-18 19:10 ` Lars Magne Ingebrigtsen
2010-10-18 20:49 ` James Cloos
2010-10-18 21:03 ` Lars Magne Ingebrigtsen
2010-10-18 23:17 ` James Cloos
2010-10-18 23:38 ` Lars Magne Ingebrigtsen
2010-10-19 16:00 ` James Cloos
2010-10-19 16:13 ` Steinar Bang
2010-10-19 18:12 ` Lars Magne Ingebrigtsen
2010-10-19 20:56 ` James Cloos
2010-10-19 18:12 ` Lars Magne Ingebrigtsen
2010-10-19 21:05 ` James Cloos
2010-10-20 0:07 ` Lars Magne Ingebrigtsen
2010-10-20 18:47 ` James Cloos
2010-10-21 15:59 ` Lars Magne Ingebrigtsen
2010-10-21 19:13 ` James Cloos
2010-10-22 14:51 ` Lars Magne Ingebrigtsen
2010-10-19 5:58 ` Steinar Bang [this message]
2010-10-19 18:11 ` 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=87zkua3erz.fsf@dod.no \
--to=sb@dod.no \
--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).