From: David Levine <levinedl@acm.org>
Date: Thu, 20 Nov 2014 03:04:33 +0000 (-0600)
Subject: Updated simple integration example in mhfixmsg(1) man page
X-Git-Url: https://diplodocus.org/git/nmh/commitdiff_plain/4835742ea8051fc7999dd994fffa18d4c7b0bd8f?hp=e8d7f6f0c0f155ccf67c10b655333cbd286fa844

Updated simple integration example in mhfixmsg(1) man page
and added return status values.
---

diff --git a/man/mhfixmsg.man b/man/mhfixmsg.man
index de5cc611..93d23aba 100644
--- a/man/mhfixmsg.man
+++ b/man/mhfixmsg.man
@@ -154,6 +154,14 @@ The
 switch directs
 .B mhfixmsg
 to output informational message for each transformation applied.
+The return status of
+.B mhfixmsg
+is 0 if all of the requested transformations are performed, or
+non-zero otherwise.
+.RB ( mhfixmsg
+will not decode to binary content, but a request to do so is
+not considered a failure, and is noted with
+.BR \-verbose .)
 .PP
 The
 .B \-file
@@ -262,12 +270,19 @@ call
 .B mhfixmsg
 immediately after a successful invocation of
 .BR inc .
-For example, with bash:
+One approach could be based on:
 .PP
 .RS 5
-alias inc='inc && mhfixmsg'
+msgs=`inc -format '%(msg)'`  &&  [ -n "$msgs" ]  &&  scan $msgs  &&  \
+mhfixmsg -nochangecur $msgs
 .RE
 .PP
+Another approach would rely on adding a sequence to Unseen-Sequence,
+which
+.B inc
+sets with the newly incorporated messages.  Those could then be
+supplied to
+.BR mhfixmsg .
 .SS "Integration with procmail"
 By way of example, here is an excerpt from a procmailrc file
 that filters messages through