X-Git-Url: http://git.marmaro.de/?p=mmh;a=blobdiff_plain;f=man%2Fmhlist.man1;h=e0724b275f6fc419267124774ea5d6907af71ddb;hp=f42498b274ccd637ac415a0fd7f74d8553b452fa;hb=5c43bb739797c078c3fd6aa982183e15af456d31;hpb=55e1d8c654ee0f7c45b9361ce34617983b454c32

diff --git a/man/mhlist.man1 b/man/mhlist.man1
index f42498b..e0724b2 100644
--- a/man/mhlist.man1
+++ b/man/mhlist.man1
@@ -18,10 +18,8 @@ mhlist \- list information about MIME messages
 .RB [ \-type
 .IR content ]
 \&...
-.RB [ \-headers " | " \-noheaders ]
-.RB [ \-realsize " | " \-norealsize ]
 .RB [ \-verbose " | " \-noverbose ]
-.RB [ \-version ]
+.RB [ \-Version ]
 .RB [ \-help ]
 .ad
 .SH DESCRIPTION
@@ -36,24 +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.
-.PP
-The
-.B \-realsize
-switch tells
-.B mhlist
-to evaluate the
-\*(lqnative\*(rq (decoded) format of each content prior to listing.
+A one-line banner is displayed above the listing.
+The size of the
+`native' (decoded) format of each content is evaluated.
 This provides an accurate count at the expense of a small delay.
-.PP
 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
@@ -62,7 +51,7 @@ 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
@@ -100,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:
@@ -123,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
@@ -147,14 +136,12 @@ multipart content (of any subtype listed above) is always acted upon.
 .fi
 
 .SH "SEE ALSO"
-mhbuild(1), mhshow(1), mhstore(1), sendfiles(1)
+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 ` \-realsize '
 .RB ` \-noverbose '
 .fi