From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] gdb: Switch "info types" over to use the gdb::options framework
Date: Fri, 12 Jul 2019 12:48:00 -0000 [thread overview]
Message-ID: <83lfx32zbt.fsf@gnu.org> (raw)
In-Reply-To: <c93fe4d308adbad677d2f2c473d26f9d1c094e7f.1562931337.git.andrew.burgess@embecosm.com> (message from Andrew Burgess on Fri, 12 Jul 2019 12:37:04 +0100)
> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Cc: Andrew Burgess <andrew.burgess@embecosm.com>
> Date: Fri, 12 Jul 2019 12:37:04 +0100
>
> Adds a new -q flag to "info types" using the gdb::option framework.
> This -q flag is similar to the -q flag already present for "info
> variables" and "info functions".
Thanks.
> diff --git a/gdb/NEWS b/gdb/NEWS
> index 4e479bf738b..cc1d58520d4 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -211,6 +211,10 @@ maint show test-options-completion-result
>
> (gdb) print -raw -pretty -object off -- *myptr
>
> + ** The "info types" command now supports the '-q' flag to disable
> + printing of some header information in a similar fashion to "info
> + variables" and "info functions".
> +
This part is OK.
> +@item info types [-q] [@var{regexp}]
> Print a brief description of all types whose names match the regular
> expression @var{regexp} (or all types in your program, if you supply
> no argument). Each complete typename is matched as though it were a
> @@ -18449,6 +18448,9 @@
> @code{whatis}, it does not print a detailed description; second, it
> lists all source files and line numbers where a type is defined.
>
> +The optional flag @samp{-q}, which stands for @samp{quiet}, disables
> +printing header information.
I don't see "headers" described anywhere in the preceding text, so
"disables printing header information" here is not clear enough.
Besides, the command's doc string says "some headers and messages",
which seems to imply more than just "headers" is suppressed by this
switch.
Can you please make the effect of this switch more clear?
Thanks.
next prev parent reply other threads:[~2019-07-12 12:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 11:37 [PATCH 0/3] Improving "info types" command Andrew Burgess
2019-07-12 11:37 ` [PATCH 1/3] gdb: Switch "info types" over to use the gdb::options framework Andrew Burgess
2019-07-12 12:48 ` Eli Zaretskii [this message]
2019-07-19 14:50 ` Andrew Burgess
2019-07-18 20:07 ` Pedro Alves
2019-07-12 11:37 ` [PATCH 3/3] gdb: Show type summary for anonymous structures from c_print_typedef Andrew Burgess
2019-07-19 12:38 ` Pedro Alves
2019-07-19 21:06 ` Andrew Burgess
2019-07-20 13:47 ` Pedro Alves
2019-07-22 14:10 ` Tom Tromey
2019-07-12 11:37 ` [PATCH 2/3] gdb: Improve output from "info types" commad Andrew Burgess
2019-07-18 20:07 ` Pedro Alves
2019-07-19 19:43 ` Andrew Burgess
2019-07-19 19:54 ` Pedro Alves
2019-07-20 13:47 ` Pedro Alves
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=83lfx32zbt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.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