Test if the buildbots care about tools/showbuildenv's exit status.

[nmh] / man / nmh.man

diff --git a/man/nmh.man b/man/nmh.man
index fd1870892012a8e69b6a31d88fbf725ceb5e7807..367a93d9a666f28c43c526188e1df5a08c46f6ad 100644 (file)
--- a/man/nmh.man
+++ b/man/nmh.man
@@ -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
 .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,
 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
 .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


@@ -540,7 +540,7 @@ contains
 .B nmh
 library commands
 .TP
 .B nmh
 library commands
 .TP

-$HOME/\&.mh\-profile
+$HOME/\&.mh_profile

 The user's nmh profile
 .ne 4
 .SH "SEE ALSO"
 The user's nmh profile
 .ne 4
 .SH "SEE ALSO"