From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
linux-man@vger.kernel.org
Subject: Re: [PATCH 4/6] time.1: ffix
Date: Fri, 28 Jul 2023 23:08:57 +0200 [thread overview]
Message-ID: <0345e25f-e440-41f4-72b6-6ed6854e4603@kernel.org> (raw)
In-Reply-To: <20230728180039.ivcnxzk66gpktqfx@illithid>
[-- Attachment #1.1: Type: text/plain, Size: 1977 bytes --]
On 2023-07-28 20:00, G. Branden Robinson wrote:
> Clean up in preparation for "MR sed".
>
> From 225f59d4bd93db69d499cfd546ebef62fc6a63cb Mon Sep 17 00:00:00 2001
> From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
> Date: Fri, 28 Jul 2023 12:02:49 -0500
> Subject: [PATCH 4/6] time.1: ffix
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
>
> Mark up ellipses properly. They should be in roman. The item preceding
> an ellipsis should be in the singular. Use unbreakable space between
> metasyntactic variable and subsequent ellipsis.
>
> Quoting groff_man_style(7):
>
> • Symbols that are neither to be typed literally nor replaced at the
> user’s discretion appear in the roman style; brackets surround
> optional arguments, and an ellipsis indicates that the previous
> syntactical element may be repeated arbitrarily.
> [...]
> • The dummy character escape sequence \& follows the ellipsis when
> further text will follow after space on the output line, keeping
> its last period from being interpreted as the end of a sentence
> and causing additional inter‐sentence space to be placed after it.
> [...]
>
> Signed-off-by: G. Branden Robinson <g.branden.robinson@gmail.com>
> ---
> man1/time.1 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man1/time.1 b/man1/time.1
> index efb818cfd..8902b4b96 100644
> --- a/man1/time.1
> +++ b/man1/time.1
> @@ -9,7 +9,7 @@ .SH NAME
> time \- time a simple command or give resource usage
> .SH SYNOPSIS
> .B time
> -.RI [ options ] " command " [ arguments... ]
> +.RI [ option \~.\|.\|.\&] " command " [ argument \~.\|.\|.]
Please document the reason why \| should be used.
Cheers,
Alex
> .SH DESCRIPTION
> The
> .B time
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-07-28 21:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 18:00 [PATCH 4/6] time.1: ffix G. Branden Robinson
2023-07-28 21:08 ` Alejandro Colomar [this message]
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=0345e25f-e440-41f4-72b6-6ed6854e4603@kernel.org \
--to=alx@kernel.org \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.org \
/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