🚀 go-pugleaf

Giving RET (vm-goto-message) a prefix argument with point in the
summary buffer fails if vm-follow-summary-cursor is non-nil and 
the cursor has moved.  I realize the doc-string says:

  If vm-follow-summary-cursor is non-nil this command first tries
  to follow the summary cursor to a new message.  If a new message
  is selected in this way, no further action is taken.  I.e. you can move
  the cursor in the summary buffer, press RETURN and select a new
  message without typing in a message number.


I often use C-v, M-v, M-<, and M-> to move around in the summary
buffer.  If I'm lucky and I land on a message I want to read, then I
can press RET.  If not, then I have to use C-p and/or C-n to get the
cursor to the right message because 3 1 RET ignores my choice of
message 31 and selects the message where the cursor is instead.  I
typically press RET with no prefix after a successful C-s in the
summary buffer, so I don't want to set vm-follow-summary-cursor to
nil.  If I give vm-goto-message a prefix argument, I would prefer that
it not be ignored.  This behavior was also present in vm5.31.

-Jerry