troff(1) input that ends a sentence at the end of the line gets the
proper inter-sentence spacing when formatted. If the sentence ends
midline then two spaces must follow to get the same result, otherwise
the spacing looks odd. Similarly, if a full stop is not the end of a
sentence then it should have the zero-width escape appended so if
re-formatting the source happens to place it at the end of the line then
no large gap follows it: e.g. `e.g.\&'.
Replace `et. al.' with `et al'.
18 files changed:
is given,
.B burst
will try to determine if the message is formatted with MIME and contains MIME parts of
is given,
.B burst
will try to determine if the message is formatted with MIME and contains MIME parts of
-type \*(lqmessage/rfc822\*(rq. If it does, it will burst the message using MIME
+type \*(lqmessage/rfc822\*(rq. If it does, it will burst the message using MIME
formatting rules. The
.B \-mime
formatting rules. The
.B \-mime
-switch can be used to enforce the use of MIME formatting. The
+switch can be used to enforce the use of MIME formatting. The
.B \-nomime
switch will force
.B burst
.B \-nomime
switch will force
.B burst
of the table of contents
of the digest, and a
.B next
of the table of contents
of the digest, and a
.B next
-to see the first message of the digest. If
+to see the first message of the digest. If
.B \-noinplace
is given, then the first message extracted from the
first digest burst becomes the current message. This leaves the context
.B \-noinplace
is given, then the first message extracted from the
first digest burst becomes the current message. This leaves the context
of messages in these folders that are in a given sequence or set of
sequences (for example the
.RI \*(lq unseen \*(rq
of messages in these folders that are in a given sequence or set of
sequences (for example the
.RI \*(lq unseen \*(rq
-sequence). This is especially
+sequence). This is especially
useful if you use some mechanism such as
.B slocal
or
useful if you use some mechanism such as
.B slocal
or
multiple sequences. If this is not given, then the default is to search
for all the sequences specified by the
.RI \*(lq Unseen-Sequence \*(rq
multiple sequences. If this is not given, then the default is to search
for all the sequences specified by the
.RI \*(lq Unseen-Sequence \*(rq
-profile component. For more details about sequences, read the
+profile component. For more details about sequences, read the
.IR mh\-sequence (5)
man page.
.PP
.IR mh\-sequence (5)
man page.
.PP
.PP
To use the MIME rules for encapsulation, specify the
.B \-mime
.PP
To use the MIME rules for encapsulation, specify the
.B \-mime
.B forw
to generate an
.B mhbuild
.B forw
to generate an
.B mhbuild
-composition file. Note that
+composition file. Note that
.B nmh
will not invoke
.B mhbuild
.B nmh
will not invoke
.B mhbuild
.BR send ,
it's possible to confuse
.B forw
.BR send ,
it's possible to confuse
.B forw
-by re\-ordering the file (e.g. by using
+by re\-ordering the file (e.g.\& by using
.RB \*(lq folder
.BR \-pack \*(rq)
before the message is successfully sent.
.RB \*(lq folder
.BR \-pack \*(rq)
before the message is successfully sent.
switch,
.B inc
will use the specified command to establish the connection to the POP
switch,
.B inc
will use the specified command to establish the connection to the POP
.IR %h
in the command will be substituted by the hostname to connect to.
.PP
.IR %h
in the command will be substituted by the hostname to connect to.
.PP
uses POP, then the
.B \-pack
.I file
uses POP, then the
.B \-pack
.I file
-switch is considered. If given, then
+switch is considered. If given, then
.B inc
simply uses the POP to
.B packf
.B inc
simply uses the POP to
.B packf
commands accept a `file' or `files' argument, and they will, if given
.B \-draftfolder
.I +folder
commands accept a `file' or `files' argument, and they will, if given
.B \-draftfolder
.I +folder
-treat these arguments as `msg' or `msgs'. (This may appear to be
-inconsistent, at first, but it saves a lot of typing) Hence,
+treat these arguments as `msg' or `msgs'. (This may appear to be
+inconsistent, at first, but it saves a lot of typing.) Hence,
.BR send ,
since when
.BR comp ,
.BR send ,
since when
.BR comp ,
.B send
directly, they supply
.B send
.B send
directly, they supply
.B send
a
.B \-draftmessage
.I msg
a
.B \-draftmessage
.I msg
.B send
is concerned, a draft folder is not being used.
.PP
.B send
is concerned, a draft folder is not being used.
.PP
escape sequences which begin with `%'. When specifying a format
string, the usual C backslash characters are honored: `\\b', `\\f',
`\\n', `\\r', and `\\t'. Continuation lines in format files end with
escape sequences which begin with `%'. When specifying a format
string, the usual C backslash characters are honored: `\\b', `\\f',
`\\n', `\\r', and `\\t'. Continuation lines in format files end with
-`\\' followed by the newline character. A literal `%' can be inserted into
+`\\' followed by the newline character. A literal `%' can be inserted into
a format file by using the sequence `%%'.
.\" TALK ABOUT SYNTAX FIRST, THEN SEMANTICS
.SS SYNTAX
a format file by using the sequence `%%'.
.\" TALK ABOUT SYNTAX FIRST, THEN SEMANTICS
.SS SYNTAX
sequences.
.PP
There are a limited number of function escapes to output terminal escape
sequences.
.PP
There are a limited number of function escapes to output terminal escape
-sequences. These sequences are retrieved from the
+sequences. These sequences are retrieved from the
.IR terminfo (5)
database according to the current terminal setting. The (\fIbold\fR\^),
(\fIunderline\fR\^), and (\fIstandout\fR\^) escapes set bold mode,
.IR terminfo (5)
database according to the current terminal setting. The (\fIbold\fR\^),
(\fIunderline\fR\^), and (\fIstandout\fR\^) escapes set bold mode,
.RE
.PP
the month and date are printed in two digits (zero filled) separated by
.RE
.PP
the month and date are printed in two digits (zero filled) separated by
.PP
.BR Resent\-cc :
.RS 5
.PP
.BR Resent\-cc :
.RS 5
-Still more recipients. See \*(lqcc:\*(rq and \*(lqResent\-To:\*(rq.
+Still more recipients. See \*(lqcc:\*(rq and \*(lqResent\-To:\*(rq.
.RE
.PP
.BR Resent\-Bcc :
.RS 5
.RE
.PP
.BR Resent\-Bcc :
.RS 5
-Even more recipients. See \*(lqBcc:\*(rq and \*(lqResent\-To:\*(rq.
+Even more recipients. See \*(lqBcc:\*(rq and \*(lqResent\-To:\*(rq.
.RE
.PP
.BR Resent\-Fcc :
.RE
.PP
.BR Resent\-Fcc :
support.
.PP
Depending on the source and target character set, it may not be possible
support.
.PP
Depending on the source and target character set, it may not be possible
-to convert all characters to the local character set. In this case a
+to convert all characters to the local character set. In this case a
substitution character will be used for the characters that cannot be
converted.
.SS
substitution character will be used for the characters that cannot be
converted.
.SS
sequence is first zero'd and then each message is added to the sequence.
Read the
.IR mh\-sequence (5)
sequence is first zero'd and then each message is added to the sequence.
Read the
.IR mh\-sequence (5)
-man page for the details about this sequence. (profile, no default)
+man page for the details about this sequence. (profile, no default)
.RE
.PP
.BR Sequence\-Negation :
.RE
.PP
.BR Sequence\-Negation :
.BR repl .
Read the
.IR mh\-draft (5)
.BR repl .
Read the
.IR mh\-draft (5)
-man page for details. (profile, no default)
+man page for details. (profile, no default)
.RE
.PP
.BI digest\-issue\- list :
.RE
.PP
.BI digest\-issue\- list :
.IR whatnowproc ,
including
one of the standard shells. As a result, it's not possible to pass
.IR whatnowproc ,
including
one of the standard shells. As a result, it's not possible to pass
-information via an argument list. The convention is that environment
+information via an argument list. The convention is that environment
variables whose names are all upper-case are user-settable; those
whose names are lower-case only are used internally by nmh and should
not generally be set by the user.
variables whose names are all upper-case are user-settable; those
whose names are lower-case only are used internally by nmh and should
not generally be set by the user.
MAILDROP
This variable tells
.B inc
MAILDROP
This variable tells
.B inc
-the default maildrop. This supersedes the \*(lqMailDrop\*(rq profile entry.
+the default maildrop. This supersedes the \*(lqMailDrop\*(rq profile entry.
.TP
MAILHOST
This variable tells
.TP
MAILHOST
This variable tells
-your mail signature. This supersedes the \*(lqSignature\*(rq profile entry,
+your mail signature. This supersedes the \*(lqSignature\*(rq profile entry,
and is not used when the \*(lqLocal\-Mailbox\*(rq profile component is set.
.TP
USER
and is not used when the \*(lqLocal\-Mailbox\*(rq profile component is set.
.TP
USER
UNIX you're running,
.B nmh
will query the system for this value
UNIX you're running,
.B nmh
will query the system for this value
-(e.g. uname, gethostname, etc.), and attempt to fully qualify this
+(e.g.\& uname, gethostname, etc.), and attempt to fully qualify this
value.
.PP
If you are using POP to retrieve new messages, you may want to set this
value.
.PP
If you are using POP to retrieve new messages, you may want to set this
This should only be needed, if for some reason
.B nmh
is not able to
This should only be needed, if for some reason
.B nmh
is not able to
-fully qualify the hostname returned by the system (e.g. uname,
+fully qualify the hostname returned by the system (e.g.\& uname,
gethostname, etc.).
.RE
.PP
gethostname, etc.).
.RE
.PP
.I mhn.defaults
entries, as usual. Text converters should limit text line lengths
to a maximum of 78 characters, and must limit them to a maximum of 998
.I mhn.defaults
entries, as usual. Text converters should limit text line lengths
to a maximum of 78 characters, and must limit them to a maximum of 998
-characters, per RFC 5322 Sec. 2.1.1.
+characters, per RFC 5322 Sec.\& 2.1.1.
.PP
Normally, addresses appearing as arguments are put in the \*(lqTo:\*(rq
field. At least one such address is required when sending a message,
.PP
Normally, addresses appearing as arguments are put in the \*(lqTo:\*(rq
field. At least one such address is required when sending a message,
-i.e., if any other switches are supplied. If the
+i.e., if any other switches are supplied. If the
.B \-cc
switch is used, all addresses following it, even if there are
intervening switches other than
.B \-cc
switch is used, all addresses following it, even if there are
intervening switches other than
-is deprecated. It is retained only
+is deprecated. It is retained only
for backwards compatibility.
.PP
You should migrate to using the
for backwards compatibility.
.PP
You should migrate to using the
-need be present in this additional profile. Finally,
+need be present in this additional profile. Finally,
.B mhshow
will attempt to consult
.PP
.B mhshow
will attempt to consult
.PP
.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,
.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
mail transport method is not in use, its addresses will be used for
delivery, and the \*(lqDcc:\*(rq field will be removed from the message. The
blind recipients will receive the same message sent to the sighted
mail transport method is not in use, its addresses will be used for
delivery, and the \*(lqDcc:\*(rq field will be removed from the message. The
blind recipients will receive the same message sent to the sighted
-recipients. *WARNING* Recipients listed in the \*(lqDcc:\*(rq field receive no
+recipients. *WARNING* Recipients listed in the \*(lqDcc:\*(rq field receive no
explicit indication that they have received a \*(lqblind copy\*(rq.
This can cause blind recipients to
inadvertently reply to all of the sighted recipients of the
explicit indication that they have received a \*(lqblind copy\*(rq.
This can cause blind recipients to
inadvertently reply to all of the sighted recipients of the
is considered delivered.
.TP \w'Azzz'u
.I R
is considered delivered.
.TP \w'Azzz'u
.I R
-Perform the action. Regardless of the outcome of the action,
+Perform the action. Regardless of the outcome of the action,
the message is not considered delivered.
.TP \w'Azzz'u
.I ?
the message is not considered delivered.
.TP \w'Azzz'u
.I ?
switch will be
read (more than one file, each preceded by
.BR \-alias ,
switch will be
read (more than one file, each preceded by
.BR \-alias ,
.IR mh\-alias (5)
for more information.
.SH FILES
.IR mh\-alias (5)
for more information.
.SH FILES