🚀 go-pugleaf

Jamie Zawinski writes:
 > I was in my inbox, with the cursor in the summary buffer.  I did
 > vm-visit-folder on some other folder.  I browsed around in that folder 
 > for a while.  When I was done, I killed it and its summary buffer.
 > VM had modified that folder even though all I had done was look at
 > messages, but I killed it without saving anyway.  Now in my inbox's
 > summary buffer, the "-->" marker is in the middle of a line, like:
 > [...]
 > and any time I type "p" or "n" I get an error:
 > 
 > Signalling: (error "Marker does not point anywhere")

  "I killed a cockroach today... it spoke to me before it died."
  "Really?  What did it say?"
  "`Crunch.'"

In other words, known bug, fixed in 5.25 and beyond.

After you killed the second folder buffer and summary buffer,
vm-message-pointer still pointed to a message in the now deceased
folder buffer.  That message in turn had markers that pointed
into the now deceased summary buffer.  Somehow these defunct
messages and markers were getting used, despite calls to
vm-set-folder-variables all over the place that were supposed to
prevent this.  As anyone who's watched horror movies knows,
disturbing the dead is never a good idea, and the result of your
encounter with them was a grimly predictable.

You're beginning to see why I got rid of vm-local-message-pointer
and vm-local-message-list.  The bugs were becoming untrackable
and unfathomable by anyone but me.  Sometimes even I couldn't
find them.  This is one of them.  I've seen this before, but
after tracing the code for a while I decided it wasn't worth the
effort.

Upgrade to at least 5.25.  If the bug is still there yell again.