man: Fix several occurences of hyphen intended to be minus.

With man pages we have to be careful or commands may not function
after copy-and-paste.
This commit is contained in:
Carl Worth 2010-04-06 18:13:33 -07:00
parent 248e6f8c04
commit e9e06d2d7c

View file

@ -256,12 +256,12 @@ takes an existing set of messages and constructs a suitable mail
template. The Reply-to header (if any, otherwise From:) is used for template. The Reply-to header (if any, otherwise From:) is used for
the To: address. Vales from the To: and Cc: headers are copied, but the To: address. Vales from the To: and Cc: headers are copied, but
not including any of the current user's email addresses (as configured not including any of the current user's email addresses (as configured
in primary_mail or other_email in the .notmuch-config file) in the in primary_mail or other_email in the .notmuch\-config file) in the
recipient list recipient list
It also builds a suitable new subject, including Re: at the front (if It also builds a suitable new subject, including Re: at the front (if
not already present), and adding the message IDs of the messages being not already present), and adding the message IDs of the messages being
replied to to the References list and setting the In-Reply-To: field replied to to the References list and setting the In\-Reply\-To: field
correctly. correctly.
Finally, the original contents of the emails are quoted by prefixing Finally, the original contents of the emails are quoted by prefixing
@ -280,8 +280,8 @@ include
.BR default .BR default
Includes subject and quoted message body. Includes subject and quoted message body.
.TP .TP
.BR headers-only .BR headers\-only
Only produces In-Reply-To, References, To, Cc, and Bcc headers. Only produces In\-Reply\-To, References, To, Cc, and Bcc headers.
.RE .RE
See the See the
@ -305,18 +305,18 @@ contents.
.RS 4 .RS 4
.TP 4 .TP 4
.BR tag " +<tag>|-<tag> [...] [--] <search-term>..." .BR tag " +<tag>|\-<tag> [...] [\-\-] <search-term>..."
Add/remove tags for all messages matching the search terms. Add/remove tags for all messages matching the search terms.
Tags prefixed by '+' are added while those prefixed by '-' are Tags prefixed by '+' are added while those prefixed by '\-' are
removed. For each message, tag removal is performed before tag removed. For each message, tag removal is performed before tag
addition. addition.
The beginning of <search-terms> is recognized by the first The beginning of <search-terms> is recognized by the first
argument that begins with neither '+' nor '-'. Support for argument that begins with neither '+' nor '\-'. Support for
an initial search term beginning with '+' or '-' is provided an initial search term beginning with '+' or '\-' is provided
by allowing the user to specify a "--" argument to separate by allowing the user to specify a "\-\-" argument to separate
the tags from the search terms. the tags from the search terms.
See the See the
@ -361,7 +361,7 @@ command can used to output a single part of a multi-part MIME message.
.RS 4 .RS 4
.TP 4 .TP 4
.BR part " --part=<part-number> <search-term>..." .BR part " \-\-part=<part-number> <search-term>..."
Output a single MIME part of a message. Output a single MIME part of a message.
@ -370,7 +370,7 @@ stdout. The search terms must match only a single message, otherwise
this command will fail. this command will fail.
The part number should match the part "id" field output by the The part number should match the part "id" field output by the
"--format=json" option of "notmuch show". If the message specified by "\-\-format=json" option of "notmuch show". If the message specified by
the search terms does not include a part with the specified "id" there the search terms does not include a part with the specified "id" there
will be no output. will be no output.
@ -438,7 +438,7 @@ as well as any other tag values added manually with
For For
.BR id: , .BR id: ,
message ID values are the literal contents of the Message-ID: header message ID values are the literal contents of the Message\-ID: header
of email messages, but without the '<', '>' delimiters. of email messages, but without the '<', '>' delimiters.
The The
@ -467,21 +467,21 @@ particular time range, (based on the Date: header) with a syntax of:
<intial-timestamp>..<final-timestamp> <intial-timestamp>..<final-timestamp>
Each timestamp is a number representing the number of seconds since Each timestamp is a number representing the number of seconds since
1970-01-01 00:00:00 UTC. This is not the most convenient means of 1970\-01\-01 00:00:00 UTC. This is not the most convenient means of
expressing date ranges, but until notmuch is fixed to accept a more expressing date ranges, but until notmuch is fixed to accept a more
convenient form, one can use the date program to construct convenient form, one can use the date program to construct
timestamps. For example, with the bash shell the folowing syntax would timestamps. For example, with the bash shell the folowing syntax would
specify a date range to return messages from 2009-10-01 until the specify a date range to return messages from 2009\-10\-01 until the
current time: current time:
$(date +%s -d 2009-10-01)..$(date +%s) $(date +%s \-d 2009\-10\-01)..$(date +%s)
.SH ENVIRONMENT .SH ENVIRONMENT
The following environment variables can be used to control the The following environment variables can be used to control the
behavior of notmuch. behavior of notmuch.
.TP .TP
.B NOTMUCH_CONFIG .B NOTMUCH_CONFIG
Specifies the location of the notmuch configuration file. Notmuch will Specifies the location of the notmuch configuration file. Notmuch will
use ${HOME}/.notmuch-config if this variable is not set. use ${HOME}/.notmuch\-config if this variable is not set.
.SH SEE ALSO .SH SEE ALSO
The emacs-based interface to notmuch (available as The emacs-based interface to notmuch (available as
.B notmuch.el .B notmuch.el