8 Commits

Author SHA1 Message Date
d843c9eb8e man: update man-pages (label / typos) 2025-08-15 21:03:19 +03:00
cee4823f33 mu-man: typeset file names using underlining
Make the emphasis more consistent, and do it using underscores in
Org documents, since verbatim is rendered as underlined anyway.
2024-07-22 15:40:57 +09:00
dcc3807155 mu-man: improve typesetting of references
Try to stick to the man-pages(7) standard.
2024-07-22 15:18:46 +09:00
96f8729cb5 mu-man: use more bold text
Make occurences of "mu", small commands such as "mu init", and
command-line arguments bold.
2024-07-18 10:01:45 +09:00
721aadc140 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>
2024-03-06 21:12:32 +00:00
c76aa53156 man: fix formatting of NAME sections
The command names are formatted inconsistently, e.g.:

    * NAME

    ~mu add~ - add one or more messages to the database

versus:

    * NAME

    *mu cfind* is the *mu* command to find contacts in the *mu* database and export them

versus:

    * NAME

    mu server - the mu backend for the mu4e e-mail client

and the format, with a space between "mu" and the subcommand, is not compatible
with mandb(8).  Use formatting which is consistent and replace the spaces with
hyphens.

Signed-off-by: Jeremy Sowden <azazel@debian.org>
2024-03-06 21:12:32 +00:00
671a958085 man: fix formatting of some man-page references
Signed-off-by: Jeremy Sowden <jeremy@azazel.net>
2023-08-19 12:00:21 +01:00
4b00ea0635 man: update man pages
Explicitly mention PCRE where appropriate.

Include section headers (through MAN_CLASS_OPTIONS)

Fix mu-easy manpage

Make date dynamic
2022-12-30 11:15:03 +02:00