Don't `else' after return. Simplify control flow.

[nmh] / man / nmh.man

diff --git a/man/nmh.man b/man/nmh.man
index b9dadd17e62c7aa27b9895370ea983e29831b48a..0c32cde52f8511f247893457892fdc0a0dbff5e3 100644 (file)
--- a/man/nmh.man
+++ b/man/nmh.man
@@ -1,4 +1,4 @@
-.TH NMH %manext7% "March 13, 2014" "%nmhversion%"
+.TH NMH %manext7% "September 26, 2016" "%nmhversion%"
 .\"
 .\" %nmhwarning%
 .\"
@@ -134,12 +134,12 @@ ambiguity with any switches that may be added in the future, it is
 recommended that full switch names be used in durable code such as
 shell scripts, functions, and aliases.
 .PP
-All the
+Each
 .B nmh
-commands may be run with the single switch
+command may be run with the single switch
 .BR \-help ,
-which causes them to print a list of the switches they may be invoked
-with and then exit.
+which causes it to print its available switches, along with any
+profile components that apply, and then exit.
 .PP
 All the
 .B nmh
@@ -209,14 +209,14 @@ Commands that take a folder name
 .BR scan,
 \&...) accept the folder name in two formats:  \*(lq+folder\*(rq or
 \*(lq@folder\*(rq.  In both cases, \*(lqfolder\*(rq can be a
-\*(lq/\*(rq-separated path, e.g. \*(lqfoo/bar\*(rq.  \*(lq+folder\*(rq
+\*(lq/\*(rq-separated path, e.g.\& \*(lqfoo/bar\*(rq.  \*(lq+folder\*(rq
 specifies a directory path to a folder.  If \*(lqfolder\*(rq starts
 with \*(lq/\*(rq then it's an absolute path from the root directory.
 If it is \*(lq.\*(rq or \*(lq..\*(rq, or starts with \*(lq./\*(rq or
 \*(lq../\*(rq, then it's relative to the current working directory.
 Otherwise it's relative to mh-profile(5)'s
 .RI \*(lq Path \*(rq,
-i.e. as given by
+i.e.\& as given by
 .RB ` "mhpath +" `.
 \*(lq@folder\*(rq is a shorthand for \*(lq+curfolder/folder\*(rq; it's
 a relative path from the current folder.  \*(lqcurfolder\*(rq is given
@@ -442,15 +442,15 @@ Convenience Wrappers
 .PD 0
 .IR mhmail (1)
 send or read mail
-.TP
-.IR msh (1)
-nmh shell
 .PD
 .ne 4
 .SS
 Utilities
 .TP \n(ttu
 .PD 0
+.IR mhfixmsg (1)
+rewrite MIME messages with various transformations
+.TP
 .IR mhparam (1)
 print nmh profile components
 .TP
@@ -474,9 +474,6 @@ Indirectly Invoked Commands
 .IR ap (8)
 parse addresses RFC 822\-style
 .TP
-.IR conflict (8)
-search for alias/password conflicts
-.TP
 .IR dp (8)
 parse dates RFC 822\-style
 .TP
@@ -533,12 +530,12 @@ contains
 .B nmh
 commands
 .TP
-%etcdir%
+%nmhetcdir%
 contains
 .B nmh
 format files
 .TP
-%libdir%
+%nmhlibexecdir%
 contains
 .B nmh
 library commands
@@ -553,14 +550,21 @@ The user's nmh profile
 .IR mh-mime (7)
 .ne 4
 .SH BUGS
+\" The contents of this section also appear in sbr/print_help.c .
+Send bug reports, questions, suggestions, and patches to
+.IR nmh-workers@nongnu.org .
+That mailing list is relatively quiet, so user questions are encouraged.
+Users are also encouraged to subscribe, and view the archives, at
+https://lists.gnu.org/mailman/listinfo/nmh-workers .
+.PP
 If problems are encountered with an
 .B nmh
-program, the problems should
+program, they should
 be reported to the local maintainers of
-.BR nmh .
-When doing this, the
-name of the program should be reported, along with the version information
-for the program.
+.BR nmh ,
+if any, or to the mailing list noted above.
+When doing this, the name of the program should be reported, along
+with the version information for the program.
 .PP
 To find out what version of an
 .B nmh
@@ -573,5 +577,4 @@ the version of
 the host it was compiled on, and the date the
 program was linked.
 .PP
-Send bug reports and suggestions to
-.IR nmh-workers@nongnu.org .
+New releases and other information of potential interest are announced at http://www.nongnu.org/nmh/ .