public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 1/9] ldconfig.8: Fix markup nits
Date: Wed, 4 Jan 2023 13:36:38 +0100	[thread overview]
Message-ID: <100b9e99-ebcf-fcfd-71b8-626448e30485@gmail.com> (raw)
In-Reply-To: <8527af62-1921-63cc-a94b-db3d9af4ee49@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 4345 bytes --]



On 1/4/23 13:26, Alejandro Colomar wrote:
> Hi Branden,
> 
> On 1/4/23 08:38, G. Branden Robinson wrote:
>> * Drop stale FIXME annotation regarding commit ID for `-i` option.
>> * Rewrite synopses to use man(7) font macros instead of *roff font
>>    selection escape sequences.
>> * Drop redundant `PD` macro calls.
>> * Rewrite option list to use man(7) font macros instead of *roff font
>>    selection escape sequences.
>> * Use `TQ` macro to include multiple tags for options with long synonyms
>>    instead of comma notation.

BTW, this would qualify as a style change (in my book, a ffix).  No?

Cheers,

Alex

>> * Break input lines after commas.
>> * Set multi-word parentheticals on their own input lines.
>> * Break input lines at phrase boundaries more often.
>> * Protect literals from automatic hyphenation with `\%` escape sequence.
>> * Use \~ escape sequence instead of quoted arguments at word
>>    boundaries in option synopses.
>>
>> Signed-off-by: G. Branden Robinson <g.branden.robinson@gmail.com>
> 
> This patch looks good to me.  However, I didn't apply it, since I have a few 
> comments below.
>> ---
>>   man8/ldconfig.8 | 109 +++++++++++++++++++++++++++++++-----------------
>>   1 file changed, 71 insertions(+), 38 deletions(-)
>>
>> diff --git a/man8/ldconfig.8 b/man8/ldconfig.8
>> index d608aaf56..0e74c1791 100644
>> --- a/man8/ldconfig.8
>> +++ b/man8/ldconfig.8
>> @@ -9,22 +9,29 @@
>>   .SH NAME
>>   ldconfig \- configure dynamic linker run-time bindings
>>   .SH SYNOPSIS
> 
> We should wrap this in .nf/.fi
> 
> Although maybe this goes better in the style patch, since it's a formatting fix.
> 
>> -.BR /sbin/ldconfig " [" \-nNvXV "] [" \-f " \fIconf\fP] [" \-C " \fIcache\fP] 
>> [" \-r " \fIroot\fP]"
>> -.IR directory \...
>>   .PD 0
>> +.\" TODO?: -c, --format, -i, --ignore-aux-cache, --print-cache,
>> +.\" --verbose, -V, --version, -?, --help, --usage
>> +.B /sbin/ldconfig
>> +.RB [ \-nNvXV ]
>> +.RB [ \-f
>> +.IR conf ]
>> +.RB [ \-C
>> +.IR cache ]
>> +.RB [ \-r
>> +.IR root ]
>> +.IR directory ...
>>   .PP
>> -.PD
>>   .B /sbin/ldconfig
>>   .B \-l
>>   .RB [ \-v ]
>> -.IR library \...
>> -.PD 0
>> +.IR library ...
>>   .PP
>> -.PD
>>   .B /sbin/ldconfig
>>   .B \-p
>> +.PD
>>   .SH DESCRIPTION
>> -.B ldconfig
>> +.B \%ldconfig
> 
> I will suggest again that I believe \% should be the default in manual pages. 
> Count how many times you want to break highlighted stuff vs how many times you 
> want to not break such stuff.
> 
>>   creates the necessary links and cache to the most recent shared
>>   libraries found in the directories specified on the command line,
>>   in the file
>> @@ -37,7 +44,8 @@ and
> 
> [...]
> 
>> @@ -105,35 +122,41 @@ Failure to follow this pattern may result in 
>> compatibility issues
>>   after an upgrade.
>>   .SH OPTIONS
>>   .TP
>> -.BR \-c " \fIfmt\fP, " \-\-format=\fIfmt\fP
>> +.BI \-c\~ fmt
>> +.TQ
>> +.BI \-\-format= fmt
>>   (Since glibc 2.2)
>> +.\" commit 45eca4d141c047950db48c69c8941163d0a61fcd
>>   Cache format to use:
>>   .IR old ,
>>   .IR new ,
>>   or
>> -.IR compat .
>> -Since glibc 2.32, the default is
>> +.IR \%compat .
>> +Since glibc 2.32,
>> +the default is
>>   .IR new .
>>   .\" commit cad64f778aced84efdaa04ae64f8737b86f063ab
>> -Before that, it was
>> -.IR compat .
>> +Before that,
>> +it was
>> +.IR \%compat .
>>   .TP
>> -.BI "\-C " cache
>> +.BI \-C\~ cache
>>   Use
>>   .I cache
>>   instead of
>>   .IR /etc/ld.so.cache .
>>   .TP
>> -.BI "\-f " conf
>> +.BI \-f\~ conf
>>   Use
>>   .I conf
>>   instead of
>>   .IR /etc/ld.so.conf .
>> -.\" FIXME glibc 2.7 added -i
> 
> And this is why comments are harmful.  I fint it rather uncommon for comments to 
> be up-to-date with the code :P
> 
>>   .TP
>> -.BR \-i ", " \-\-ignore\-aux\-cache
>> +.B \-i
>> +.TQ
>> +.B \-\-ignore\-aux\-cache
>>   (Since glibc 2.7)
>> -.\"             commit 27d9ffda17df4d2388687afd12897774fde39bcc
>> +.\" commit 27d9ffda17df4d2388687afd12897774fde39bcc
>>   Ignore auxiliary cache file.
>>   .TP
>>   .B \-l
>> @@ -154,31 +177,40 @@ Implies
> 
> [...]
> 
> 

-- 
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-01-04 12:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04  7:38 [PATCH 1/9] ldconfig.8: Fix markup nits G. Branden Robinson
2023-01-04 12:26 ` Alejandro Colomar
2023-01-04 12:36   ` Alejandro Colomar [this message]
2023-01-04 16:06     ` G. Branden Robinson
2023-01-04 15:55   ` G. Branden Robinson
2023-01-04 18:41     ` Alejandro Colomar
2023-01-04 19:11       ` G. Branden Robinson
2023-01-04 20:15         ` Alejandro Colomar
2023-01-04 20:59           ` G. Branden Robinson
2023-01-05  1:21             ` 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=100b9e99-ebcf-fcfd-71b8-626448e30485@gmail.com \
    --to=alx.manpages@gmail.com \
    --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