From: Dave Abrahams <dave@boostpro.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org, John Wiegley <johnw@boostpro.com>
Subject: Re: Updated IMAP unread count correction
Date: Mon, 17 Sep 2012 15:06:16 -0400 [thread overview]
Message-ID: <m28vc8a2qf.fsf@pluto.luannocracy.com> (raw)
In-Reply-To: <m2vcfs9r2i.fsf@boostpro.com> (Dave Abrahams's message of "Wed, 05 Sep 2012 13:01:57 -0700")
on Wed Sep 05 2012, Dave Abrahams <dave-AT-boostpro.com> wrote:
> on Wed Sep 05 2012, Lars Ingebrigtsen <larsi-AT-gnus.org> wrote:
>
>> Dave Abrahams <dave@boostpro.com> writes:
>>
>>>>> So, again, I dearly wish for a way to flush all that state so I can get
>>>>> back to a "clean state."
>>>>
>>>> Yes, that would be nice. But no such thing exists.
>>>
>>> Can you give any hints about how to get there?
>>
>> At this point, your guess is as good as mine. There's the Agent, and
>> the cache, and possibly some of the sync stuff, and possibly some
>> non-server marks...
>
> This is why I avoid as many of those mechanisms as possible and try to
> talk directly to a local server for everything.
>
>>
>>> Oh... well, under normal circumstances there's no way to tell whether
>>> it's working or waiting for network traffic, right?
>>
>> Usually you're able to make an educated guess based on what Gnus is
>> saying. Like "opening server..." and stuff.
>
> Sure, but then there's a race condition. If you decide to hit `C-g' and
> Gnus decides to finish its remote work before the `C-g' is processed,
> you've just trashed Gnus' state.
Soooo... is this just not a concern for you? It just occurred to me
that I commonly hit `C-g' several times in a row, so when the 2nd one
gets processed Gnus is almost *guaranteed* not to be waiting for network
traffic, right?
--
Dave Abrahams
BoostPro Computing Software Development Training
http://www.boostpro.com Clang/LLVM/EDG Compilers C++ Boost
next prev parent reply other threads:[~2012-09-17 19:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 21:08 Dave Abrahams
2012-06-10 19:36 ` Lars Magne Ingebrigtsen
2012-06-10 21:07 ` Dave Abrahams
2012-06-10 21:13 ` Lars Magne Ingebrigtsen
2012-06-10 21:25 ` Dave Abrahams
2012-06-10 21:39 ` Lars Magne Ingebrigtsen
2012-06-10 22:03 ` Dave Abrahams
2012-06-10 22:12 ` Lars Magne Ingebrigtsen
2012-06-11 14:53 ` Julien Cubizolles
2012-09-05 14:04 ` Lars Ingebrigtsen
2012-06-12 14:29 ` Dave Abrahams
2012-09-05 14:05 ` Lars Ingebrigtsen
2012-09-05 17:20 ` Dave Abrahams
2012-09-05 17:56 ` Lars Ingebrigtsen
2012-09-05 19:41 ` Dave Abrahams
2012-09-05 19:46 ` Lars Ingebrigtsen
2012-09-05 20:01 ` Dave Abrahams
2012-09-17 19:06 ` Dave Abrahams [this message]
2012-12-25 12:24 ` Lars Ingebrigtsen
2012-07-11 13:25 ` Myles
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=m28vc8a2qf.fsf@pluto.luannocracy.com \
--to=dave@boostpro.com \
--cc=ding@gnus.org \
--cc=johnw@boostpro.com \
--cc=larsi@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).