🚀 go-pugleaf

From: "Barton E. Schaefer" <island!ucbcad!cse.ogc.edu!schaefer>

In article <7330016@grlab.UUCP> you write:
} 1) Mail forwarding (with edit)
}    I used to use 'mail -f .' (or more precisely I bound the macro
}    '[mail-flags]-f .' to \CF) to forward mail to people with editing. It
}    seems that the newest mush (Mail User's Shell (6.5 4/17/89) [5/19/89])
}    and it ships my forwarded mail off without allowing me to edit it.

Use '[mail-flags]-ef\n'		# the -e is for "edit"

The consensus of some earlier discussion was that $autoedit should not
affect "mail -f", so to get editing you need to explicitly give -e.

} 2) Interrupt handling in the new await command.
}    It seems to interrupt the macro sequence for the following macro and
}    leave me in [line-mode]. Is it suppose to do that?
}       [line-mode]\nupdate\nawait\nsort -d\ncurses\n[first-msg]

It isn't the await command that's breaking the macro, it's the sort.
Macros by definition abort if any component fails.  If there is only
one message in the mailbox, sort will fail with "not enough messages"
or something like that.

}    I suppose a solution to this would be to use:
}       [line-mode]update\n[line-mode]await\n[sort-reverse]d[first-msg]

That will do what you want, because if [sort-reverse] fails you will be
left on the first (only) message, even though the macro aborts.  If you
try to do anything more, like

    ...await\n[sort-reverse]d[first-msg][display]

then I'd expect that the [display] would not happen when only one message
has come in, again because of the sort failure.

} Thanx,
} Scott Blachowicz
} USPS:  Graphicus                UUCP:    ...!hpubvwa!grlab!scott

-- 
Bart Schaefer       "And if you believe that, you'll believe anything."
							-- DangerMouse
CSNET / Internet                schaefer@cse.ogc.edu
UUCP                            ...{sequent,tektronix,verdix}!ogccse!schaefer