man: change quoting style
The man-page sources use single quotes to quote text. However, this can be
problematic in man-pages because if a single quote appears at the beginning of a
line the following word is interpreted by troff as a macro. For example, this
paragraph in mu-easy.7:
What if we want to see some of the body of the message? You can get a 'summary'
of the first lines of the message using the \fI\-\-summary\-len\fP option, which will
'summarize' the first \fIn\fP lines of the message:
elicits this warning:
$ man --warnings obj-x86_64-linux-gnu/man/mu-easy.7 >/dev/null
troff:<standard input>:166: warning: macro 'summarize'' not defined
and gets truncated:
What if we want to see some of the body of the message? You can get a
'summary' of the first lines of the message using the --summary-len op‐
tion, which will
One could adjust the line-wrapping to move the quoted text away from the
beginning of the line, but that is fragile. Another possibility would be to use
the troff escape-sequences for open and close quotes (`\(oq` and `\(cq`
respectively), but ox-man is being used precisely to avoid having to handle
troff directly. Instead use back-ticks for left quotes. Thus:
What if we want to see some of the body of the message? You can get a `summary'
of the first lines of the message using the \fI\-\-summary\-len\fP option, which will
`summarize' the first \fIn\fP lines of the message:
which is rendered correctly:
What if we want to see some of the body of the message? You can get a
`summary' of the first lines of the message using the --summary-len op-
tion, which will `summarize' the first n lines of the message:
Signed-off-by: Jeremy Sowden <azazel@debian.org>
This commit is contained in:
@ -27,9 +27,9 @@ performed).
|
||||
|
||||
** --my-address=<email-address-or-regex>
|
||||
|
||||
specifies that some e-mail address is 'my-address' (the option can be used
|
||||
specifies that some e-mail address is `my-address' (the option can be used
|
||||
multiple times). Any message in which at least one of the contact fields
|
||||
contains such an address is considered a 'personal' messages; this can then be
|
||||
contains such an address is considered a `personal' messages; this can then be
|
||||
used for filtering in *mu-find(1)*, *mu-cfind(1)* and *mu4e*, e.g. to filter-out
|
||||
mailing list messages.
|
||||
|
||||
@ -58,7 +58,7 @@ the number of changes after which they are committed to the database; decreasing
|
||||
the value reduces the memory requirements, at the cost of make indexing
|
||||
substantially slower. Usually, the default of 250000 should be fine.
|
||||
|
||||
Batch-size 0 is interpreted as 'use the default'.
|
||||
Batch-size 0 is interpreted as `use the default'.
|
||||
|
||||
** --support-ngrams
|
||||
|
||||
@ -76,7 +76,7 @@ options.
|
||||
|
||||
* NGRAM SUPPORT
|
||||
|
||||
*mu*'s underlying Xapian database supports 'ngrams', which improve searching for
|
||||
*mu*'s underlying Xapian database supports `ngrams', which improve searching for
|
||||
languages/scripts that do not have explicit word breaks, such as Chinese,
|
||||
Japanese and Korean. It is fairly intrusive, and influences both indexing and
|
||||
query-parsing; it is not enabled by default, and is recommended only if you need
|
||||
|
||||
Reference in New Issue
Block a user