Gnus development mailing list
 help / color / mirror / Atom feed
From: Joseph Barillari <jbarilla@princeton.edu>
Subject: Re: Losing `expirable' marks in nnimap groups
Date: Sun, 07 Jul 2002 16:26:45 -0400	[thread overview]
Message-ID: <m3u1nb708q.fsf@washer.barillari.org> (raw)
In-Reply-To: <20020707200815.GA20165@zork.net> (Sean Neakums's message of "Sun, 07 Jul 2002 21:08:15 +0100")

[-- Attachment #1: Type: text/plain, Size: 1845 bytes --]

>>>>> "SN" == Sean Neakums <sneakums@zork.net> writes:

    SN> commence Kai Gro?johann quotation:
    >> Dan Christensen <jdc@uwo.ca> writes:
    >> 
    >> > Hmm, I can't reproduce this anymore.
    >> 
    >> I've also not seen lost expirable marks in the last 1 or 2
    >> days.  Fascinating.  A Heisenbug is when the behavior is
    >> unpredictable.  So is a Schroederbug the case where the bug
    >> goes away if you look for it?

    SN> I always thought the latter definition was that of a
    SN> Heisenbug.  I had one of those once, but I've forgotten the
    SN> details.  I recall it involved some C code and gdb.

I'll second that. So does the Jargon File[0]:

# heisenbug /hi:'zen-buhg/ n.

# [from Heisenberg's Uncertainty Principle in quantum physics] A bug
# that disappears or alters its behavior when one attempts to probe or
# isolate it.

Conversely, a 'schroedinbug' is "A design or implementation bug in a
program that doesn't manifest until someone reading source or using
the program in an unusual way notices that it never should have
worked, at which point the program promptly stops working for
everybody until fixed."

An "unpredictable" (quoth Kai) bug is a mandelbug:

# [from the Mandelbrot set] A bug whose underlying causes are so complex
# and obscure as to make its behavior appear chaotic or even
# non-deterministic. This term implies that the speaker thinks it is a
# Bohr bug, rather than a heisenbug. See also schroedinbug.

--Joe

[0] http://www.tuxedo.org/~esr/jargon/html/The-Jargon-Lexicon-framed.html[1]

[1] Is there a gnus add-on for auto-numbering footnotes like these?
    Can one, for instance, use a LaTeX-like syntactic construct to
    indicate footnote content, and run a function to process the
    footnotes before sending the message?
    

[-- Attachment #2: Type: application/pgp-signature, Size: 258 bytes --]

  reply	other threads:[~2002-07-07 20:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-05 14:14 Kai Großjohann
2002-07-05 14:47 ` Simon Josefsson
2002-07-06  3:08 ` Dan Christensen
2002-07-06 10:30   ` Simon Josefsson
2002-07-07 17:07     ` Dan Christensen
2002-07-07 19:34       ` Simon Josefsson
2002-07-07 20:03       ` Kai Großjohann
2002-07-07 20:08         ` Sean Neakums
2002-07-07 20:26           ` Joseph Barillari [this message]
2002-07-07 20:31             ` Sean Neakums
2002-07-07 20:14         ` Paul Jarc
2002-07-06 20:26 ` Wes Hardaker

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=m3u1nb708q.fsf@washer.barillari.org \
    --to=jbarilla@princeton.edu \
    /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).