From: Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/doc]: Updated manpages to be consistent with help
Date: Wed, 13 Oct 2021 12:03:51 -0300 [thread overview]
Message-ID: <f439f5a7-fd78-a6f5-cc74-81f451edbf7a@redhat.com> (raw)
In-Reply-To: <83bl3tniel.fsf@gnu.org>
On 10/13/21 10:50 AM, Eli Zaretskii wrote:
>> Date: Wed, 13 Oct 2021 10:04:09 -0300
>> From: Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org>
>>
>> Updated manpages to be consistent with help information provided by the
>> binary. The main changes are Making all long-form options have '--',
>> instead of a single '-' and added most of the missing options to the
>> manpage.
>
> Thanks. The replacement of '-' by '--' are mechanical and don't need
> any approval.
>
> Many other changes replace something like this:
>
> Use @file{file} as SOMETHING.
>
> with something like this:
>
> Use file @file{somefile} as SOMETHING.
>
> I must confess that I prefer the former form, because it makes the
> text more concise and easier to read, by avoiding one more "file".
>
Thanks for the review. This change in specific, I understand why you may not be a fan, but the idea was to sync between manpages and --help, and since help calls those "somefile" instead of just "file" I thought it was worth doing. I can roll them back, but I think the --help text should be changed to be the same generic file. Same goes for DIR and directory, which you mention below. Up to your preferences which of those I do.
I'll implement to all the other style changes you mentioned. It could be worth adding them to the Documentation writing standard (https://sourceware.org/gdb/wiki/Internals%20GDB-Doc-Standards) since that page is almost empty.
>> -@item -nh
>> +@item --directory=@var{DIR}
>> +@itemx -d @var{DIR}
>> +Add @var{DIR} to the path to search for source files.
>
> The string inside @var{..} should never be upper-case. (Yes, I know
> this was in the original text.)
>
> Also, here I'd prefer
>
> Add @var{directory} to the path to search for source files.
>
> because "DIR" doesn't necessarily speak for its being a directory.
>
--
Cheers!
Bruno Larsen
next prev parent reply other threads:[~2021-10-13 15:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 13:04 Bruno Larsen via Gdb-patches
2021-10-13 13:50 ` Eli Zaretskii via Gdb-patches
2021-10-13 15:03 ` Bruno Larsen via Gdb-patches [this message]
2021-10-13 15:30 ` Sergio Durigan Junior via Gdb-patches
2021-10-14 13:10 ` Bruno Larsen via Gdb-patches
2021-10-14 18:56 ` Philippe Waroquiers via Gdb-patches
2021-10-15 13:27 ` Bruno Larsen via Gdb-patches
2021-10-16 11:44 ` Philippe Waroquiers via Gdb-patches
2021-10-19 13:24 ` Bruno Larsen via Gdb-patches
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=f439f5a7-fd78-a6f5-cc74-81f451edbf7a@redhat.com \
--to=gdb-patches@sourceware.org \
--cc=blarsen@redhat.com \
--cc=eliz@gnu.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