🚀 go-pugleaf

On the same vein of possible problems with deleted messages and
the current message pointer:  Using curses mode, say I've got a
list of deleted messages that I've also saved in various ways such
that the S flag is set.  If I undelete the message, mush moves the
current message pointer to the next message following the deleted
messages which hasn't been S'd.  This is annoying, because I
sometimes backtrack to a saved&deleted message to look at it again,
and mush goes off and assumes it knows better than me which message
I want.  This is irregardless of the setting of `autoprint', btw.

Oh, I just discovered out my +rr and -rr map!ings (see earlier
ravings about ~ commands) are rendered effectiveless by edit_hdrs,
as mush apparently builds headers once and then never changes
them(*) when edit_hdrs is set.  This seems to be an offshoot of
the same problem with ~h and friends when edit_hdrs is in effect.
The obvious solution is to add the R-R-T header in the editor (I
am now), but this requires the addition of a macro in the editor
to define this in an appropriate, mail-composition-only way.

As a question to Dan or Bart: how `alpha' is 7.0 for those non-sunview
users among us?

John <LoVerso@Xylogics.COM>

(*) There is an exception to this, the `From:' header, which I wish
    mush would either not supply (sendmail would do it right) or let
    me supply it as `From: "Full User Name" <mailbox>'.  I detest the
    `(Full User Name) mailbox' form, as in the latter the () surround
    a comment that mail system gateways (into X.400, for instance) are
    allowed to discard at will.  When I had more time, I'd go in and
    rip and tear the From: code in mush, but I've got bits to push!