X-Git-Url: https://diplodocus.org/git/nmh/blobdiff_plain/000c879060454bf1a5a883542cf5f8f721951203..54fb590089a2bf43d7987861ba57acb17cebc150:/man/mh-sequence.man?ds=sidebyside

diff --git a/man/mh-sequence.man b/man/mh-sequence.man
index 6590e5b6..dd14973a 100644
--- a/man/mh-sequence.man
+++ b/man/mh-sequence.man
@@ -1,7 +1,7 @@
-.TH MH-SEQUENCE %manext5% "March 23, 2017" "%nmhversion%"
-.\"
+.TH MH-SEQUENCE %manext5% 2013-10-17 "%nmhversion%"
+.
 .\" %nmhwarning%
-.\"
+.
 .SH NAME
 mh-sequence \- sequence specification for nmh message system
 .SH DESCRIPTION
@@ -39,7 +39,7 @@ the message numerically following \*(lqcur\*(rq
 .PD
 .PP
 In commands that take a `msg' argument, the default is \*(lqcur\*(rq.
-As a shorthand, \*(lq\&.\*(rq is equivalent to \*(lqcur\*(rq.
+As a shorthand, \*(lq.\*(rq is equivalent to \*(lqcur\*(rq.
 .PP
 For example: In a folder containing five messages numbered 5, 10, 94, 177
 and 325, \*(lqfirst\*(rq is 5 and \*(lqlast\*(rq is 325.  If \*(lqcur\*(rq
@@ -139,7 +139,7 @@ public and private.  Public sequences of a folder are accessible to any
 user that can read that folder.  They are kept in each folder
 in the file determined by the \*(lqmh\-sequences\*(rq profile entry
 (default is
-.IR \&.mh\(rusequences ).
+.IR \&.mh_sequences ).
 Private sequences are accessible
 only to the
 .B nmh
@@ -160,7 +160,7 @@ For most commands, this can be overridden by using the switches
 .B \-public
 and
 .BR \-private .
-But if the folder is read\-only, or if
+But if the folder is read-only, or if
 the \*(lqmh\-sequences\*(rq profile entry is defined but empty, then
 \fIprivate\fR sequences will be created instead.
 .SS "Sequence Negation"
@@ -218,14 +218,14 @@ there can be a performance penalty in using the
 .B all
 .B nmh
 programs have to write the sequence information to the
-.I \&.mh\(rusequences
+.I \&.mh_sequences
 file for the folder each time they run.  If the
 \*(lqPrevious\-Sequence\*(rq profile entry is not included, only
 .B pick
 and
 .B mark
 will write to the
-.B \&.mh\(rusequences
+.B \&.mh_sequences
 file.
 .SS "The Unseen Sequence"
 Finally, many users like to indicate which messages have not been
@@ -238,7 +238,7 @@ and
 .B show
 honor the profile entry \*(lqUnseen\-Sequence\*(rq to support this
 activity.  This entry in the
-.I \&.mh\(ruprofile
+.I \&.mh_profile
 should be defined as one or more sequence names, as separate arguments.
 If there is a value for \*(lqUnseen\-Sequence\*(rq in the profile,
 then whenever new messages are placed in a folder (using
@@ -257,7 +257,7 @@ directs
 to add new messages to the sequence \*(lqunseen\*(rq.
 Unlike the behavior of the \*(lqPrevious\-Sequence\*(rq entry in the
 profile, however, the sequence(s) will
-.B not
+.I not
 be zeroed by
 .BR inc .
 .PP
@@ -303,7 +303,7 @@ commands are run simultaneously.
 commands that modify the sequence file use transactional locks; the lock
 is held from the time the sequence file is read until it it written out.
 This ensures that modifications to the sequence file will not be lost
-if multiple commands are run simultaneously.  Long\-running
+if multiple commands are run simultaneously.  Long-running
 .B nmh
 commands, such as
 .B inc
@@ -313,7 +313,7 @@ will release the sequence lock during the bulk of their runtime and reread
 the sequence file after their processing is complete to reduce lock
 contention time.
 .PP
-.B Note:
+Note:
 Currently transactional locks are only supported for public sequences;
 private sequences will not get corrupted, but the possibility exists that two
 .B nmh
@@ -322,13 +322,13 @@ one command's messages not appearing on the requested sequence.
 .SH FILES
 .PD 0
 .TP 20
-$HOME/\&.mh\-profile
+$HOME/.mh\-profile
 The user's profile.
 .TP 20
-<mh\-dir>/context
+<mh-dir>/context
 The user's context.
 .TP 20
-<folder>/\&.mh\-sequences
+<folder>/.mh\-sequences
 File for public sequences.
 .PD
 .SH "PROFILE COMPONENTS"