From: Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>,
Sergio Durigan Junior <sergiodj@sergiodj.net>,
Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] [gdb/doc]: Updated manpages to be consistent with help
Date: Tue, 19 Oct 2021 10:24:33 -0300 [thread overview]
Message-ID: <9c0d3c63-e5d3-cb02-f952-578a4a1caa4e@redhat.com> (raw)
In-Reply-To: <a45116e550aac20adefb4bda561291c3d6253839.camel@skynet.be>
On 10/16/21 08:44, Philippe Waroquiers wrote:
> On Fri, 2021-10-15 at 10:27 -0300, Bruno Larsen wrote:
>> On 10/14/21 15:56, Philippe Waroquiers wrote:
>>> Note that I started a patch to have the options consistently using --
>>>
>>> But as GDB accepts various layout for options (such as -thisone or --thisone),
>>> it was not very clear it that was a good thing to do.
>>> Pedro e.g. commented that GDB does not use the concept of 'short' and 'long' options.
>>>
>>> Finally, as I understand, the decision was rather to use as cannnical form
>>> -thisone
>>> (in the doc and on line help)
>>> and so the manual should then also be aligned.
>>>
>>> Sadly, I had no time to finalize the patch (i.e. to rather systematically use
>>> the single dash convention).
>>> But this patch seems then not to go into what I think is the last agreed direction.
>>>
>>> See the initial RFC in
>>> https://sourceware.org/pipermail/gdb-patches/2021-June/179587.html
>>> and RFA in
>>> https://sourceware.org/pipermail/gdb-patches/2021-June/179834.html
>>>
>>> Thanks
>>> Philippe
>>>
>>
>> Hi! I didn't see this patch when writing my own, sorry.
>>
>> As for not going the agreed direction, it didn't sounds "agreed" to me, since Eli agreed with documenting '--' while Pedro preferred '-'. I agree with the argument that GDB doesn't accept short options, since you can't combine them, but the help page still shows the abbreviated versions with a single dash and longer versions with '--' and that causes confusion for users. What the patches are supposed to do is make those 2 pages consistent and avoid user confusion, keeping them as-is because the developers know it makes more sense doesn't fix confusion.
>>
>> My proposed solution is: Let's make them consistent with help, all longer options having '--', use your text explaining that GDB accepts all 8 versions of options despite how they are written, but change it to call "abbreviated" and "longer" options instead, to avoid the "short option" confusion that Pedro has brought up. Does that sound reasonable?
>>
>
> See also the feedback of Joel.
> https://sourceware.org/pipermail/gdb-patches/2021-August/181294.html
>
> Philippe
>
>
Having looked at that e-mail, I think the new version is conforming to the agreed direction of documenting that GDB doesn't care about - or --, but still document it as traditional argument handling does: https://sourceware.org/pipermail/gdb-patches/2021-October/182632.html
Thanks for the resources and for looking at the patch
--
Cheers!
Bruno Larsen
prev parent reply other threads:[~2021-10-19 13:26 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
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 [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=9c0d3c63-e5d3-cb02-f952-578a4a1caa4e@redhat.com \
--to=gdb-patches@sourceware.org \
--cc=blarsen@redhat.com \
--cc=philippe.waroquiers@skynet.be \
--cc=sergiodj@sergiodj.net \
/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