linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alejandro Colomar <colomar.6.4.3@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH 1/2] system_data_types.7: srcfix
Date: Sun, 27 Sep 2020 22:24:19 +0200	[thread overview]
Message-ID: <bff2769a-8999-b658-6bb3-5b4bfa8255d0@gmail.com> (raw)
In-Reply-To: <20200927061015.4obt73pdhyh7wecu@localhost.localdomain>

Hi Branden,

On 2020-09-27 08:10, G. Branden Robinson wrote:
 > At 2020-09-25T10:03:30+0200, Alejandro Colomar wrote:
 >> @@ -454,7 +454,7 @@ Used for a count of elements, and array indices.
 >>   It is the result of subtracting two pointers.
 >>   According to the C language standard, it shall be a signed integer 
type
 >>   capable of storing values in the range
 >> -.BR "" [ PTRDIFF_MIN ,
 >> +.RB [ PTRDIFF_MIN ,
 >>   .BR PTRDIFF_MAX ].
 >>   .IP
 >>   The length modifier for
 >
 > Ooh, thanks for that.  The deleted line is a terrible anti-pattern and
 > you're doing everyone a solid by removing the temptation to copy it.

Yup, I introduced that line a few patches ago because
I didn't know .RB existed :)

BTW, thanks for all your comments.
Thanks to them I improved the style in system_data_types.7,
which I started a few weeks ago.

Thanks,

Alex

 >
 > groff_man_style(7) attempts to lead people to the light:
 >
 >   Optional macro arguments are indicated by surrounding them with square
 >   brackets.  If a macro accepts multiple arguments, those containing
 >   space characters must be double-quoted to be interpreted correctly.  An
 >   empty macro argument can be specified with a pair of double-quotes
 >   (“""”), but the man package is designed such that this should seldom be
 >   necessary.  Unused macro arguments are more often simply omitted, or
 >   good style suggests that a more appropriate macro be chosen, that ear‐
 >   lier arguments are more important than later ones, or that arguments
 >   have identical significance such that skipping any is superfluous.
 >
 > ...but alas, groff 1.22.5, or 1.23 or whatever we call it, is not yet
 > released.
 >
 > Regards,
 > Branden
 >

  reply	other threads:[~2020-09-27 20:24 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-25  8:03 [PATCH 1/2] system_data_types.7: srcfix Alejandro Colomar
2020-09-25  8:03 ` [PATCH 2/2] " Alejandro Colomar
2020-09-25 10:40   ` Michael Kerrisk (man-pages)
2020-09-25 11:28     ` [PATCH v2 " Alejandro Colomar
2020-09-25 12:02       ` Michael Kerrisk (man-pages)
2020-09-25 12:46         ` Alejandro Colomar
2020-09-25 10:39 ` [PATCH 1/2] " Michael Kerrisk (man-pages)
2020-09-27  6:10 ` G. Branden Robinson
2020-09-27 20:24   ` Alejandro Colomar [this message]
2020-09-28 12:58     ` G. Branden Robinson
2020-09-28 13:29   ` Jakub Wilk
2020-09-28 13:40     ` G. Branden Robinson
2020-09-29 12:13     ` Michael Kerrisk (man-pages)
2020-09-30 10:12       ` G. Branden Robinson
2022-08-19 18:03         ` Jakub Wilk
2022-08-19 23:53           ` Alejandro Colomar
2022-08-20  5:43           ` G. Branden Robinson
2022-08-20 11:57             ` .TH 4th field (Was: [PATCH 1/2] system_data_types.7: srcfix) Alejandro Colomar
2022-08-20 12:20               ` G. Branden Robinson
2022-08-20 12:40                 ` Alejandro Colomar
2022-08-20 13:04                   ` Alejandro Colomar
2022-08-21 11:46                   ` Alejandro Colomar
2022-08-24 13:22                   ` Ingo Schwarze
2022-08-24 15:04                     ` Alejandro Colomar
2022-08-24 17:12                       ` Ingo Schwarze
2022-08-24 19:37                         ` Alejandro Colomar

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=bff2769a-8999-b658-6bb3-5b4bfa8255d0@gmail.com \
    --to=colomar.6.4.3@gmail.com \
    --cc=g.branden.robinson@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).