[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bb43d258-e3e8-ea4b-fcf1-6e9d280dd85e@gmail.com>
Date: Sat, 3 Oct 2020 13:47:08 +0200
From: Alejandro Colomar <colomar.6.4.3@...il.com>
To: "G. Branden Robinson" <g.branden.robinson@...il.com>
Cc: "Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>,
Paul Eggert <eggert@...ucla.edu>, linux-man@...r.kernel.org,
gcc-patches@....gnu.org, libc-alpha@...rceware.org,
linux-kernel@...r.kernel.org, jwakely.gcc@...il.com,
David.Laight@...LAB.COM
Subject: Re: [PATCH v4 1/2] system_data_types.7: Add 'void *'
On 10/3/20 9:48 AM, G. Branden Robinson wrote:
[...]
>> The "short" answer[1] is that I think Alex is correct; Paul's caution is
>> unwarranted and arises from confusion with the font alternation macros
>> of the man(7) macro package. Examples of the latter are .BI and .BR.
>> Those set their even-numbered arguments in one font and odd-numbered
>> arguments in another, with no space between them. That suppression of
>> space is the reason they exist. With the "single-font" macros like .B
>> and .I[2], if you don't want space, don't type it.
Hi Branden,
This explanation is great :)
Would you mind writing a patch with it?
Cheers,
Alex
>>
>> I could say more, including an annotated explanation of the groff and
>> Version 7 Unix man(7) implementations of the I macro, if desired. :)
:)
>>
>> Regards,
>> Branden
>>
>> [1] since as everyone knows, I struggle with brevity
>> [2] I (and others) discourage use of .SM and .SB because they can't be
>> distinguished from ordinary roman and bold type, respectively, on
>> terminals.
>>
Powered by blists - more mailing lists