lock_file.c: close(2) file descriptor on failure, avoiding leak.

[nmh] / man / mark.man

diff --git a/man/mark.man b/man/mark.man
index 74bdfe6cefdda0a484d597f169c65a9449f21038..130bce6f1992fe886d33402326e2248bfa49319f 100644 (file)
--- a/man/mark.man
+++ b/man/mark.man
@@ -1,38 +1,38 @@
-.TH MARK %manext1% "February 11, 2012" "%nmhversion%"
-.\"
+.TH MARK %manext1% 2013-03-31 "%nmhversion%"
+.
 .\" %nmhwarning%
-.\"
+.
 .SH NAME
-mark \- manipulate message sequences
+mark \- manipulate nmh message sequences
 .SH SYNOPSIS
 .HP 5
 .na
 .B mark
+.RB [ \-help ]
+.RB [ \-version ]
 .RI [ +folder ]
 .RI [ msgs ]
 .RB [ \-sequence
 .I name
 \&...]
 .RB [ \-add " | " \-delete ]
-.RB [ \-list ] 
+.RB [ \-list ]
 .RB [ \-public " | " \-nopublic ]
 .RB [ \-zero " | " \-nozero ]
-.RB [ \-version ]
-.RB [ \-help ]
 .ad
 .SH DESCRIPTION
 The
 .B mark
 command manipulates message sequences by adding or deleting
-message numbers from folder\-specific message sequences, or by listing
+message numbers from folder-specific message sequences, or by listing
 those sequences and messages.
 .PP
 A message sequence is a keyword, just like one of the \*(lqreserved\*(rq
 message names, such as \*(lqfirst\*(rq or \*(lqnext\*(rq.  Unlike the
 \*(lqreserved\*(rq message names, which have a fixed semantics on
-a per\-folder basis, the semantics of a message sequence may be
+a per-folder basis, the semantics of a message sequence may be
 defined, modified, and removed by the user.  Message sequences are
-folder\-specific, e.g., the sequence name \*(lqseen\*(rq in the context
+folder-specific, e.g., the sequence name \*(lqseen\*(rq in the context
 of folder
 .RI \*(lq +inbox \*(rq
 need not have any relation whatsoever to the
@@ -97,8 +97,8 @@ As expected, the command
 .B \-sequence
 .I foo
 .B \-delete
-all\*(rq
-deletes the sequence \*(lqfoo\*(rq from the current folder.
+all\*(rq empties the sequence \*(lqfoo\*(rq, and therefore removes
+that sequence from the current folder's list of sequences.
 .PP
 When creating or modifying sequences, you can specify the switches
 .B \-public
@@ -118,9 +118,9 @@ sequences should be made \*(lqprivate\*(rq, and will only be accessible by
 you.  If neither of these switches is specified, then existing sequences
 will maintain their current status, and new sequences will default to
 \*(lqpublic\*(rq if you have write permission for the relevant folder.
-Check the
+Check
 .IR mh\-sequence (5)
-man page for more details about the difference
+for more details about the difference
 between \*(lqpublic\*(rq and \*(lqprivate\*(rq sequences.
 .PP
 The
@@ -129,7 +129,7 @@ switch tells
 .B mark
 to list both the sequences defined
 for the folder and the messages associated with those sequences.
-.B Mark
+.B mark
 will list the name of each sequence given by
 .B \-sequence
 .I name
@@ -143,7 +143,7 @@ will be listed.  The
 switch does not affect the operation of
 .BR \-list .
 .PP
-The current restrictions on sequences are:
+The restrictions on sequences are:
 .PP
 .IP \(bu 2
 The name used to denote a message sequence must consist of an alphabetic
@@ -152,20 +152,14 @@ be one of the (reserved) message names \*(lqnew\*(rq, \*(lqfirst\*(rq,
 \*(lqlast\*(rq, \*(lqall\*(rq, \*(lqnext\*(rq, or \*(lqprev\*(rq.
 .PP
 .IP \(bu 2
-Only a certain number of sequences may be defined for a given folder.
-This number is usually limited to 27 (11 on small systems).  (The
-internal implementation relies on bitmasks, with some bits set aside
-for internal use.)
-.PP
-.IP \(bu 2
-Message ranges with user\-defined sequence names are restricted to the
+Message ranges with user-defined sequence names are restricted to the
 form \*(lqname:n\*(rq, \*(lqname:+n\*(rq, or \*(lqname:-n\*(rq, and refer
 to the first or last `n' messages of the sequence `name', respectively.
 Constructs of the form \*(lqname1\-name2\*(rq are forbidden for user
 defined sequences.
 .SH FILES
 .TP 20
-$HOME/.mh\-profile
+$HOME/.mh_profile
 The user's profile.
 .SH "PROFILE COMPONENTS"
 .PD 0