These tools are shell scripts and thus have a different option
processing mechanism than the other mmh tools. Unfortunately, it
is limited: Options must come first.
Also note that mhpgp accepts a +folder argument, and what the
defaults are.
.na
.B mhpgp
.RB [ \-write ]
-.RI [ msg ]
.RB [ \-Version ]
.RB [ \-help ]
+.RI [ +folder ]
+.RI [ msg ]
.ad
.SH DESCRIPTION
.B mhpgp
mhsign(1), gpg(1)
.SH DEFAULTS
-None
+.nf
+.RB ` +folder "' defaults to the current folder"
+.RB ` msg "' defaults to the current message"
+.fi
.SH CONTEXT
None
.SH BUGS
-None
+The order of the command line arguments is relevant: The options
+must come first, the message specification last.
.B mhsign
.RB [ \-encrypt ]
.RB [ \-mime ]
-.I file
.RB [ \-Version ]
.RB [ \-help ]
+.I file
.ad
.SH DESCRIPTION
.B mhsign
None
.SH BUGS
-None
+The order of the command line arguments is relevant: Options must
+come first, the file must be last.
# mhpgp:
# -write: Save the decrypted message to the current folder
-usage="Usage: mhpgp [-write] msg"
+usage="Usage: mhpgp [-write] [-Version] [-help] [+folder] [msg]"
# prepend the default options from the profile
set -- `mhparam -nocomp ${0##*/}` "$@"
# will be removed and any "From " line will be indented for
# best compatibility. Enforced for multipart messages.
-usage="Usage: mhsign [-encrypt] [-mime] file"
+usage="Usage: mhsign [-encrypt] [-mime] [-Version] [-help] file"
# defaults
usemime=n