X-Git-Url: http://git.marmaro.de/?p=mmh;a=blobdiff_plain;f=man%2Fmhlist.man1;h=90f46cc82b17fb2cb46c31b5d7a1376b29f42b0e;hp=193695902a8189c1a46154952f9afffffa14f2e2;hb=18591f8e001ecedbee48a51c1d1f08ebaa1c15c8;hpb=8d8f1c3abc586c005c904e52c4adbfe694d2201c

diff --git a/man/mhlist.man1 b/man/mhlist.man1
index 1936959..90f46cc 100644
--- a/man/mhlist.man1
+++ b/man/mhlist.man1
@@ -18,9 +18,8 @@ mhlist \- list information about MIME messages
 .RB [ \-type
 .IR content ]
 \&...
-.RB [ \-headers " | " \-noheaders ]
 .RB [ \-verbose " | " \-noverbose ]
-.RB [ \-version ]
+.RB [ \-Version ]
 .RB [ \-help ]
 .ad
 .SH DESCRIPTION
@@ -35,18 +34,15 @@ manipulates MIME (multi-media messages) as specified
 in RFC\-2045 thru RFC\-2049 (See
 .BR mhbuild (1)).
 .PP
-The
-.B \-headers
-switch indicates that a one-line banner should be
-displayed above the listing.
+A one-line banner is displayed above the listing.
 The size of the
-\*(lqnative\*(rq (decoded) format of each content is evaluated.
+`native' (decoded) format of each content is evaluated.
 This provides an accurate count at the expense of a small delay.
 If the
 .B \-verbose
 switch is present, then the listing will show
-any \*(lqextra\*(rq information that is present in the message,
-such as comments in the \*(lqContent-Type\*(rq header.
+any `extra' information that is present in the message,
+such as comments in the `Content-Type' header.
 .PP
 The option
 .B \-file
@@ -55,18 +51,18 @@ directs
 .B mhlist
 to use the specified
 file as the source message, rather than a message from a folder.
-If you specify this file as \*(lq-\*(rq, then
+If you specify this file as `-', then
 .B mhlist
 will
 accept the source message on the standard input.  Note that the
 file, or input from standard input should be a validly formatted
 message, just like any other
-.B nmh
+.B mh
 message.  It should
 .B NOT
 be in mail drop format (to convert a file in mail drop format to
 a folder of
-.B nmh
+.B mh
 messages, see
 .BR inc (1)).
 .PP
@@ -93,7 +89,7 @@ kind of content, or if the part is itself another multipart content, the
 switch will not prevent the content from being acted upon.
 .PP
 A content specification consists of a content type and a subtype.
-The initial list of \*(lqstandard\*(rq content types and subtypes can
+The initial list of `standard' content types and subtypes can
 be found in RFC\-2046.
 .PP
 A list of commonly used contents is briefly reproduced here:
@@ -116,8 +112,8 @@ video	mpeg
 A legal MIME message must contain a subtype specification.
 .PP
 To specify a content, regardless of its subtype, just use the
-name of the content, e.g., \*(lqaudio\*(rq.  To specify a specific
-subtype, separate the two with a slash, e.g., \*(lqaudio/basic\*(rq.
+name of the content, e.g., `audio'.  To specify a specific
+subtype, separate the two with a slash, e.g., `audio/basic'.
 Note that regardless of the values given to the
 .B \-type
 switch, a
@@ -145,8 +141,7 @@ mhbuild(1), show(1), mhstore(1), sendfiles(1)
 .SH DEFAULTS
 .nf
 .RB ` +folder "' defaults to the current folder"
-.RB ` msgs "' defaults to cur"
-.RB ` \-headers '
+.RB ` msgs "' defaults to the current message"
 .RB ` \-noverbose '
 .fi