From: Rocco Rutte Date: Sat, 4 Apr 2009 11:54:47 +0000 (+0200) Subject: Manual: Use — in text rather than -- X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=17d859756c9530ecd885ecc74ac6cd60932d99a9;p=neomutt Manual: Use — in text rather than -- --- diff --git a/doc/manual.xml.head b/doc/manual.xml.head index c160507e2..61f2e8c2f 100644 --- a/doc/manual.xml.head +++ b/doc/manual.xml.head @@ -2861,7 +2861,7 @@ With various functions, Mutt will treat messages differently, depending on whether you sent them or whether you received them from someone else. For instance, when replying to a message that you sent to a different party, Mutt will automatically suggest to send -the response to the original message's recipients -- responding to +the response to the original message's recipients — responding to yourself won't make much sense in many cases. (See $reply_to.) @@ -3679,7 +3679,7 @@ Your first step is to define your external filter's spam patterns using the spam command. pattern should be a regular expression that matches a header in a mail message. If any message in the mailbox matches this regular expression, it will receive a spam tag or -spam attribute (unless it also matches a nospam pattern -- see +spam attribute (unless it also matches a nospam pattern — see below.) The appearance of this attribute is entirely up to you, and is governed by the format parameter. format can be any static text, but it also can include back-references from the pattern @@ -3718,7 +3718,7 @@ If then a message is received that DCC registered with many hits under the Fuz2 checksum, and that PureMessage registered with a 97% probability of being spam, that message's spam tag would read 90+/DCC-Fuz2, 97/PM. (The four characters before =many in a -DCC report indicate the checksum used -- in this case, Fuz2.) +DCC report indicate the checksum used — in this case, Fuz2.) @@ -3743,12 +3743,12 @@ to sorting. -Generally, when you sort by spam tag, Mutt will sort lexically -- +Generally, when you sort by spam tag, Mutt will sort lexically — that is, by ordering strings alphanumerically. However, if a spam tag begins with a number, Mutt will sort numerically first, and lexically only when two numbers are equal in value. (This is like UNIX's -sort -n.) A message with no spam attributes at all -- that is, one -that didn't match any of your spam patterns -- is sorted at +sort -n.) A message with no spam attributes at all — that is, one +that didn't match any of your spam patterns — is sorted at lowest priority. Numbers are sorted next, beginning with 0 and ranging upward. Finally, non-numeric strings are sorted, with a taking lower priority than z. Clearly, in general, sorting by spam tags is most @@ -3776,7 +3776,7 @@ and nospam in conjunction with a folder-hook You can have as many spam or nospam commands as you like. -You can even do your own primitive spam detection within Mutt -- for +You can even do your own primitive spam detection within Mutt — for example, if you consider all mail from MAILER-DAEMON to be spam, you can use a spam command like this: @@ -4205,9 +4205,9 @@ minimum and maximum size of the resulting string, as well as its justification. If the - sign follows the percent, the string will be left-justified instead of right-justified. If there's a number immediately following that, it's the minimum amount of space the -formatted string will occupy -- if it's naturally smaller than that, it +formatted string will occupy — if it's naturally smaller than that, it will be padded out with spaces. If a decimal point and another number -follow, that's the maximum space allowable -- the string will not be +follow, that's the maximum space allowable — the string will not be permitted to exceed that width, no matter its natural size. Each of these three elements is optional, so that all these are legal format strings: %-12s, %4c, @@ -4219,7 +4219,7 @@ Mutt adds some other modifiers to format strings. If you use an equals symbol (=) as a numeric prefix (like the minus above), it will force the string to be centered within its minimum space range. For example, %=14y will reserve 14 -characters for the %y expansion -- that's the X-Label: header, in +characters for the %y expansion — that's the X-Label: header, in $index_format. If the expansion results in a string less than 14 characters, it will be centered in a 14-character space. If the X-Label for a message were test, that @@ -4827,19 +4827,19 @@ patterns: -! -- logical NOT operator +! — logical NOT operator -| -- logical OR operator +| — logical OR operator -() -- logical grouping operator +() — logical grouping operator @@ -5353,49 +5353,49 @@ work at the beginning of a string. -! -- refers to your $spoolfile (incoming) mailbox +! — refers to your $spoolfile (incoming) mailbox -> -- refers to your $mbox file +> — refers to your $mbox file -< -- refers to your $record file +< — refers to your $record file -ˆ -- refers to the current mailbox +ˆ — refers to the current mailbox -- or !! -- refers to the file you've last visited +- or !! — refers to the file you've last visited -˜ -- refers to your home directory +˜ — refers to your home directory -= or + -- refers to your $folder directory += or + — refers to your $folder directory -@alias -- refers to the default save folder as determined by the address of the alias +@alias — refers to the default save folder as determined by the address of the alias @@ -6549,7 +6549,7 @@ The syntax is: -disposition is the attachment's Content-Disposition type -- either +disposition is the attachment's Content-Disposition type — either inline or attachment. You can abbreviate this to I or A. @@ -6577,7 +6577,7 @@ The MIME types you give to the attachments directive are a kind of pattern. When you use the attachments directive, the patterns you specify are added to a list. When you use unattachments, the pattern is removed from the list. The patterns are not expanded and matched -to specific MIME types at this time -- they're just text in a list. +to specific MIME types at this time — they're just text in a list. They're only matched when actually evaluating a message.