From xemacs-m  Sat Mar 22 14:08:59 1997
Received: from GS213.SP.CS.CMU.EDU (GS213.SP.CS.CMU.EDU [128.2.209.183])
	by xemacs.org (8.8.5/8.8.5) with SMTP id OAA29939
	for <xemacs-beta@xemacs.org>; Sat, 22 Mar 1997 14:08:59 -0600 (CST)
Received: by GS213.SP.CS.CMU.EDU (AIX 3.2/UCB 5.64/4.03)
          id AA36261; Sat, 22 Mar 1997 15:08:54 -0500
Date: Sat, 22 Mar 1997 15:08:54 -0500
Message-Id: <9703222008.AA36261@GS213.SP.CS.CMU.EDU>
From: Darrell Kindred <dkindred@cmu.edu>
To: xemacs-beta@xemacs.org
Cc: Kyle Jones <kyle_jones@wonderworks.com>
Subject: Re: possible VM bug [no bug]
Organization: Carnegie Mellon University School of Computer Science
In-Reply-To: <QQchzp19714.199703221721@crystal.WonderWorks.COM>
References: <9703220724.AA31857@GS213.SP.CS.CMU.EDU>
	<QQchzp19714.199703221721@crystal.WonderWorks.COM>

Kyle Jones writes:
 > Barry's question is still open: do bugs naturally clump toward
 > the end of a release cycle, or do we all just suck?

Well, in this case I think you're clear.  Which is not to
say we all don't suck.

 > I've never seen this behavior.  I'm trying to figure out how
 > you're ending up in vm-gobble-crash-box with a zero length
 > crash box file, since it should never be called unless there's
 > a non-zero length crash box.

As I mentioned earlier, we have some local hacks to
vm-folder.el to support our funky local mail-retrieval
method.  I can provide details if you're curious, but
basically we have to bypass the zero-size check that
appears in vm-get-spooled-mail, so we do end up in
vm-gobble-crash-box with an empty crash-box.

 > But you've apparently found a way, so the code should be fixed to
 > deal with it.

If it's easy enough to modify vm-gobble-crash-box to handle
an empty crashbox, that would be great, and might make it
less likely for such bugs to crop up in the future.
But it looks like this is not important for unmodified VM,
so feel free to ignore it.

- Darrell

