🚀 go-pugleaf

Here is my Unix mailbox before running vm5.31:

^A^A^A^A
Delivery-Date: Wed, 29 Jan 92 16:03:53 EST
Received:  by echidna.ch.apollo.hp.com id <AA01967@echidna.ch.apollo.hp.com>; Wed, 29 Jan 1992 20:57:22 GMT    
Date: wed, 29 jan 92 20:57:22
From:  kissel (Rick Kissel)
To:  kissel
Subject:  test

bar.
^A^A^A^A

It is just mmdf format, and I have changed the nulls to ^A to get
through the mail system.

Here is my vm inbox after invoking vm5.31 when my inbox was empty (i.e.
did not exist) and the above mail was in my Unix mailbox:

^A^A^A^A
Delivery-Date: Wed, 29 Jan 92 16:03:53 EST
Received:  by echidna.ch.apollo.hp.com id <AA01967@echidna.ch.apollo.hp.com>; Wed, 29 Jan 1992 20:57:22 GMT    
Date: wed, 29 jan 92 20:57:22
From:  kissel (Rick Kissel)
To:  kissel
Subject:  test

bar.
^A^A^A^A

VM said "getting new messages" and then "no new messages" and the mode
line says "VM 5.31 (beta): inbox (no messages)".  But, the lines above
are displayed in the buffer.  If I do an "h" command to generate a
summary I get the following traceback:

Signalling: (folder-empty)
  signal(folder-empty nil)
  (while ...)
  vm-error-if-folder-empty()
  vm-summarize(1)
* call-interactively(vm-summarize)

If I then say "q" and leave vm and then reinvoke it with ESC-x vm, everything is fine.  It says
there is one new message, the summary is right, etc.  This has been happening for a long time, I
think I first mentioned it in an early beta release.  What I do is just always leave at least
one message in my inbox and then there is no problem.  I tried to track down the problem once
but did not succeed.  It is clearly somewhere where the folder type is initialized and the fact
that the inbox is empty means that vm doesn't know that it will be in mmdf format after the new
mail is picked up.

 -- Rick