🚀 go-pugleaf

In vm5.31 using Emacs 18.55.

1. After reading my 7th message and saving it using vm-save-message, and
because I have (setq vm-delete-after-saving t), my Summary window
looked like:

-> 1   F   LAN'S GROUP PE  Tue Apr  9 01:24 120/4834  "Trip delay               " 
   2  DF   Gary Andrew FM2 Tue Apr  9 08:02 125/4975  "He's misinterpreted the c" 
   3       JULIE LUNDBERG  Tue Apr  9 11:21  54/1654  "I need T3 Transfer Info!!" 
   4  DF   JAMES HILL FM2- Tue Apr  9 11:53  75/1411  "packing list of items bei" 
   5  DF   JAMES HILL FM2- Tue Apr  9 13:11  77/1469  "revised packing list for " 
   6  DF   ibm1::breyerrob Tue Apr  9 13:21  51/2325  "Re: traip delay          " 
   7  DF   Kevin Davis     Tue Apr  9 13:26  61/1657  "status update            " 

Then, when I typed vm-previous-message, I got the minibuffer error

Args out of range: 0,1

and my backtrace was:

Signalling: (args-out-of-range 0 1)
  narrow-to-region(#<marker at 1 in INBOX> 0)
  (let ...)
  (progn ...)
  (unwind-protect ...)
  (let ...)
  (vm-within-current-message-buffer ...computing arguments...)
  (let ...)
  vm-preview-current-message()
  (progn ...)
  (if ...)
  (let ...)
  vm-next-message(-1 1 1)
  vm-previous-message(1 1 1)
* call-interactively(vm-previous-message)


2. There is also a minor typo in vm-auto-next-message that I found
along the way:

vm-auto-next-message's value is nil

Documentation:
*Non-nil value causes VM to use vm-next-mesage to advance to the next
                                        ^^^^^^
message in the folder if the user attempts to scroll past the end of the
current messages.  A nil value disables this behavior.