README.manpages: `user ID', not `user-id'.

[nmh] / man / mh-format.man

diff --git a/man/mh-format.man b/man/mh-format.man
index 6356d68e734670bd306d386e4d12afbeffae565d..59d55d607f4bd2068f3c93c9522f071d2094a9ad 100644 (file)
--- a/man/mh-format.man
+++ b/man/mh-format.man
@@ -1,7 +1,7 @@
-.TH MH-FORMAT %manext5% "December 18, 2016" "%nmhversion%"
-.\"
+.TH MH-FORMAT %manext5% 2015-01-10 "%nmhversion%"
+.

 .\" %nmhwarning%
 .\" %nmhwarning%

-.\"
+.

 .SH NAME
 mh-format \- format file for nmh message system
 .SH DESCRIPTION
 .SH NAME
 mh-format \- format file for nmh message system
 .SH DESCRIPTION


@@ -115,7 +115,7 @@ These are combined into the conditional execution construct:
 .nf
 .RI "%< " condition " " "format-text"
 .RI "%? " condition " " "format-text"
 .nf
 .RI "%< " condition " " "format-text"
 .RI "%? " condition " " "format-text"

-    \&...
+    ...

 .RI "%| " "format-text"
 %>
 .fi
 .RI "%| " "format-text"
 %>
 .fi


@@ -123,7 +123,7 @@ These are combined into the conditional execution construct:
 .PP
 (Extra white space is shown here only for clarity.)
 These constructs, which may be nested without ambiguity, form a general
 .PP
 (Extra white space is shown here only for clarity.)
 These constructs, which may be nested without ambiguity, form a general

-.B if\-elseif\-else\-endif
+.B if-elseif-else-endif

 block where only one of the format-texts is interpreted.  In other
 words, `%<' is like the "if", `%?' is like the "elseif", `%|' is like
 "else", and `%>' is like "endif".
 block where only one of the format-texts is interpreted.  In other
 words, `%<' is like the "if", `%?' is like the "elseif", `%|' is like
 "else", and `%>' is like "endif".


@@ -249,7 +249,7 @@ size                integer size of message
 strlen         integer length of \fIstr\fR
 width          integer column width of terminal
 charleft               integer bytes left in output buffer
 strlen         integer length of \fIstr\fR
 width          integer column width of terminal
 charleft               integer bytes left in output buffer

-timenow                integer seconds since the UNIX epoch
+timenow                integer seconds since the Unix epoch

 me             string  the user's mailbox (username)
 myhost         string  the user's local hostname
 myname         string  the user's name
 me             string  the user's mailbox (username)
 myhost         string  the user's local hostname
 myname         string  the user's name


@@ -366,7 +366,7 @@ szone       date    integer timezone explicit?
 date2local     date            coerce date to local timezone
 date2gmt       date            coerce date to GMT
 dst    date    integer daylight savings in effect? (0 or 1)
 date2local     date            coerce date to local timezone
 date2gmt       date            coerce date to GMT
 dst    date    integer daylight savings in effect? (0 or 1)

-clock  date    integer seconds since the UNIX epoch
+clock  date    integer seconds since the Unix epoch

 rclock date    integer seconds prior to current time
 tws    date    string  official RFC 822 rendering
 pretty date    string  user-friendly rendering
 rclock date    integer seconds prior to current time
 tws    date    string  official RFC 822 rendering
 pretty date    string  user-friendly rendering


@@ -532,7 +532,7 @@ register for the width) a better implementation would look like:
 .PP
 It should be noted here that the side effects of function and component
 escapes are still in force and, as a result, each component test in the
 .PP
 It should be noted here that the side effects of function and component
 escapes are still in force and, as a result, each component test in the

-.B if\-elseif\-else\-endif
+.B if-elseif-else-endif

 clause sets the
 .I str
 register.
 clause sets the
 .I str
 register.