that command line arguments must be quoted for protection from
the shell. That's not a bug, and has nothing to do with nmh.
Changed "back-quoted" to "backquoted" for consistency in a few
man pages.
-.TH AP %manext8% "March 6, 2012" "%nmhversion%"
+.TH AP %manext8% "November 6, 2012" "%nmhversion%"
-.SH BUGS
-The argument to the
-.B \-format
-switch must be interpreted as a single token
-by the shell that invokes
-.BR ap .
-Therefore,
-one must usually place the argument to this switch inside quotes.
-.TH DP %manext8% "March 6, 2012" "%nmhversion%"
+.TH DP %manext8% "November 6, 2012" "%nmhversion%"
-.SH BUGS
-The argument to the
-.B \-format
-switch must be interpreted as a single token by the shell that invokes
-.BR dp .
-Therefore, one must usually place the argument to this switch inside quotes.
-.TH INC %manext1% "July 1, 2012" "%nmhversion%"
+.TH INC %manext1% "November 6, 2012" "%nmhversion%"
option is specified. This leaves the context ready for a
.B show
of the first new message.
option is specified. This leaves the context ready for a
.B show
of the first new message.
-.SH BUGS
-The argument to the
-.B \-format
-switch must be interpreted as a single
-token by the shell that invokes
-.BR inc .
-Therefore, one must usually place the argument to this switch inside
-quotes.
-.TH MH-DRAFT %manext5% "January 2, 2001" "%nmhversion%"
+.TH MH-DRAFT %manext5% "November 6, 2012" "%nmhversion%"
.B scan
the folder to see which message draft in the
folder should be used for editing or sending. Clever users could even
.B scan
the folder to see which message draft in the
folder should be used for editing or sending. Clever users could even
.B pick
to do the work:
.PP
.B pick
to do the work:
.PP
-.TH MH-PROFILE %manext5% "October 15, 2012" "%nmhversion%"
+.TH MH-PROFILE %manext5% "November 6, 2012" "%nmhversion%"
.PP
Blank lines are not permitted in
.IR \&.mh\(ruprofile.
.PP
Blank lines are not permitted in
.IR \&.mh\(ruprofile.
+The shell quoting conventions are not available in the
+.IR \&.mh\(ruprofile ;
+each token is separated by whitespace.
.SS "Standard Profile Entries"
The possible profile components are exemplified below. The only mandatory
entry is `Path:'. The others are optional; some have default values if
.SS "Standard Profile Entries"
The possible profile components are exemplified below. The only mandatory
entry is `Path:'. The others are optional; some have default values if
directory. As a result, you can actually have more than one set of
private sequences by using different context files.
.SH BUGS
directory. As a result, you can actually have more than one set of
private sequences by using different context files.
.SH BUGS
-The shell quoting conventions are not available in the
-.IR \&.mh\(ruprofile .
-Each token is separated by whitespace.
-.PP
There is some question as to what kind of arguments should be placed
in the profile as options. In order to provide a clear answer, recall
command line semantics of all
There is some question as to what kind of arguments should be placed
in the profile as options. In order to provide a clear answer, recall
command line semantics of all
-.TH MHPARAM %manext1% "June 14, 2012" "%nmhversion%"
+.TH MHPARAM %manext1% "November 6, 2012" "%nmhversion%"
-is also useful in back\-quoted operations:
+is also useful in backquoted operations:
-.TH MHPATH %manext1% "February 18, 2012" "%nmhversion%"
+.TH MHPATH %manext1% "November 6, 2012" "%nmhversion%"
-is also useful in back\-quoted operations:
+is also useful in backquoted operations:
+Because
+.B mhpath
+expands and sorts
+.RI [ msgs ].
+the command
+.PP
+.RS 5
+.nf
+mv `mhpath 501 500`
+.fi
+.RE
+.PP
+to will not move 501 to 500.
+Quite the reverse. But
+.PP
+.RS 5
+.nf
+mv `mhpath 501` `mhpath 500`
+.fi
+.RE
+.PP
+will do the trick.
+.PP
+Out of range message 0 is treated far more severely than large out of
+range message numbers.
-.SH BUGS
-Like all
-.B nmh
-commands,
-.B mhpath
-expands and sorts
-.RI [ msgs ].
-So don't
-expect
-.PP
-.RS 5
-.nf
-mv `mhpath 501 500`
-.fi
-.RE
-.PP
-to move 501 to 500.
-Quite the reverse. But
-.PP
-.RS 5
-.nf
-mv `mhpath 501` `mhpath 500`
-.fi
-.RE
-.PP
-will do the trick.
-.PP
-Out of range message 0 is treated far more severely than large out of
-range message numbers.
-.TH MSH %manext1% "January 8, 2012" "%nmhversion%"
+.TH MSH %manext1% "November 6, 2012" "%nmhversion%"
.PP
When parsing commands to the left of any redirection symbol,
.B msh
.PP
When parsing commands to the left of any redirection symbol,
.B msh
-will honor `\\' (back\-slash) as the quote next\-character symbol, and
+will honor `\\' (backslash) as the quote next\-character symbol, and
`\*(lq' (double\-quote) as quote\-word delimiters. All other input tokens
are separated by whitespace (spaces and tabs).
.SH FILES
`\*(lq' (double\-quote) as quote\-word delimiters. All other input tokens
are separated by whitespace (spaces and tabs).
.SH FILES
.SH CONTEXT
None
.SH BUGS
.SH CONTEXT
None
.SH BUGS
-The argument to the
-.B \-prompt
-switch must be interpreted as a single
-token by the shell that invokes
-.BR msh .
-Therefore, one must usually
-place the argument to this switch inside double\-quotes.
.PP
There is a strict limit of messages per file in
.BR packf 'd
.PP
There is a strict limit of messages per file in
.BR packf 'd
.PP
In particular,
.B msh
.PP
In particular,
.B msh
-does not understand back\-quoting, so the only
+does not understand backquoting, so the only
effective way to use
.B pick
inside
effective way to use
.B pick
inside
-.TH PICK %manext1% "March 6, 2012" "%nmhversion%"
+.TH PICK %manext1% "November 6, 2012" "%nmhversion%"
to enumerate the messages in a sequence
(such as for use by a shell script).
.SH BUGS
to enumerate the messages in a sequence
(such as for use by a shell script).
.SH BUGS
-The argument to the
-.B \-after
-and
-.B \-before
-switches must be interpreted
-as a single token by the shell that invokes
-.BR pick .
-Therefore, one
-must usually place the argument to this switch inside quotes.
-Furthermore, any occurrence of
.B \-datefield
must occur prior to the
.B \-after
.B \-datefield
must occur prior to the
.B \-after
-is used in a back\-quoted operation, such as
+is used in a backquoted operation, such as
.PP
.RS 5
scan\0`pick\0\-from\0jones`
.PP
.RS 5
scan\0`pick\0\-from\0jones`
-.TH SCAN %manext1% "November 4, 2012" "%nmhversion%"
+.TH SCAN %manext1% "November 6, 2012" "%nmhversion%"
a heading saying what each column in the listing was. Format strings
prevent this from happening.
.SH BUGS
a heading saying what each column in the listing was. Format strings
prevent this from happening.
.SH BUGS
-The argument to the
-.B \-format
-switch must be interpreted as a single
-token by the shell that invokes
-.BR scan .
-Therefore, one must usually
-place the argument to this switch inside quotes.
-.PP
The value of each
.I component
escape is set by
The value of each
.I component
escape is set by
-.TH WHATNOW %manext1% "April 4, 2012" "%nmhversion%"
+.TH WHATNOW %manext1% "November 6, 2012" "%nmhversion%"
.RB ` \-attach "' defaults to \*(lqNmh-Attachment\*(rq"
.fi
.SH BUGS
.RB ` \-attach "' defaults to \*(lqNmh-Attachment\*(rq"
.fi
.SH BUGS
-The argument to the
-.B \-prompt
-switch must be interpreted as a single
-token by the shell that invokes
-.BR whatnow .
-Therefore, one must
-usually place the argument to this switch inside quotes.
-.PP
If the initial edit fails,
.B whatnow
deletes your draft (by renaming
If the initial edit fails,
.B whatnow
deletes your draft (by renaming