From: Dave Abrahams <dave@boostpro.com>
To: ding@gnus.org
Subject: Re: Reviving Gnus after suspend/hibernation
Date: Fri, 21 Oct 2011 19:58:02 -0400 [thread overview]
Message-ID: <m262jhdhit.fsf@pluto.luannocracy.com> (raw)
In-Reply-To: <8762jiz3fh.fsf@dod.no>
on Fri Oct 21 2011, Steinar Bang <sb-AT-dod.no> wrote:
>>>>>> ludo@gnu.org (Ludovic Courtès):
>> Dave Abrahams <dave@boostpro.com> skribis:
>
>>> Beware: Lars has said that if you hit C-g while Gnus is working on
>>> something its data structures may be corrupted.
>
>> Hmm, scary!
>
> I hit C-g all of the time, on one of my emacsen, when it's stuck.
>
> And so far it has always recovered.
Whether or not it does may depend on lots of things: backends, agent,
cache, etc. Lars has said the code is generally not designed to handle
arbitrary quit's, and I take him at his word.
Except in purely-functional languages where there is no mutation,
invariants are regularly broken and fixed up (e.g. if two lists are
supposed to be the same length, you ultimately have to modify them one
at a time). If a quit is thrown while invariants are broken, they'll
stay that way.
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
next prev parent reply other threads:[~2011-10-21 23:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 16:39 Ludovic Courtès
2011-10-18 17:15 ` Richard Riley
2011-10-18 18:00 ` Tassilo Horn
2011-10-18 19:14 ` Dave Abrahams
2011-10-19 6:20 ` Tassilo Horn
2011-10-21 15:31 ` Ludovic Courtès
2011-10-21 16:59 ` Steinar Bang
2011-10-21 23:58 ` Dave Abrahams [this message]
2011-10-22 9:07 ` Steinar Bang
2011-10-22 20:29 ` Dave Abrahams
2011-10-18 19:13 ` Dave Abrahams
2011-10-24 13:23 ` Ted Zlatanov
2011-10-27 17:41 ` Ted Zlatanov
2011-10-27 18:30 ` Jonas Hörsch
2011-10-28 16:27 ` Richard Riley
2011-10-29 19:07 ` Antoine Levitt
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=m262jhdhit.fsf@pluto.luannocracy.com \
--to=dave@boostpro.com \
--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).