From: Jakub Wilk <jwilk@jwilk.net>
To: Alejandro Colomar <colomar.6.4.3@gmail.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>, <linux-man@vger.kernel.org>
Subject: Re: \- vs - (Was [Re: [PATCH 2/3] system_data_types.7: Add 'clock_t'])
Date: Mon, 19 Oct 2020 20:10:47 +0200 [thread overview]
Message-ID: <20201019181047.palj3nbvozlvnoqg@jwilk.net> (raw)
In-Reply-To: <706d3eea-60f8-c208-0cd4-3412ebfef263@gmail.com>
* Alejandro Colomar <colomar.6.4.3@gmail.com>, 2020-10-19, 19:40:
>Then, in the following code (taken from printf.3)
>the escape is wrong (unneeded) by those guidelines?:
>
>[[
>.SH NAME
>printf, fprintf, dprintf, sprintf, snprintf, vprintf, vfprintf, vdprintf,
>vsprintf, vsnprintf \- formatted output conversion
>]]
From the typographical point of view, the most appropriate character
here would be \(en (en-dash); but for historical reasons, you're
supposed to use \- (minus sign). This is documented in the man(7) manual
page, section "Sections".
--
Jakub Wilk
next prev parent reply other threads:[~2020-10-19 18:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 21:37 [PATCH 1/3] system_data_types.7: time_t: Add Versions note Alejandro Colomar
2020-10-17 21:37 ` [PATCH 2/3] system_data_types.7: Add 'clock_t' Alejandro Colomar
2020-10-18 5:56 ` Michael Kerrisk (man-pages)
2020-10-18 9:10 ` Alejandro Colomar
2020-10-18 13:09 ` Michael Kerrisk (man-pages)
2020-10-19 17:40 ` \- vs - (Was [Re: [PATCH 2/3] system_data_types.7: Add 'clock_t']) Alejandro Colomar
2020-10-19 18:10 ` Jakub Wilk [this message]
2020-10-19 22:11 ` Alejandro Colomar
2020-10-21 21:19 ` G. Branden Robinson
2020-10-17 21:37 ` [PATCH 3/3] clock_t.3: New link to system_data_types(3) Alejandro Colomar
2020-10-18 16:52 ` Michael Kerrisk (man-pages)
2020-10-18 1:05 ` [PATCH 1/3] system_data_types.7: time_t: Add Versions note Paul Eggert
2020-10-18 5:46 ` Michael Kerrisk (man-pages)
2020-10-18 9:02 ` Alejandro Colomar
2020-10-18 13:05 ` Michael Kerrisk (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201019181047.palj3nbvozlvnoqg@jwilk.net \
--to=jwilk@jwilk.net \
--cc=colomar.6.4.3@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).