Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFAv2 5/6] Announce changes in NEWS to info [args|functions|locals|variables]
Date: Mon, 27 Aug 2018 04:39:00 -0000	[thread overview]
Message-ID: <1535344760.1438.13.camel@skynet.be> (raw)
In-Reply-To: <83pny556qj.fsf@gnu.org>

Thanks for the review, I will do the updates as suggested
in this and the other mail.

One question below.

Philippe


On Sun, 2018-08-26 at 21:21 +0300, Eli Zaretskii wrote:
> > From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
> > Cc: Philippe Waroquiers <philippe.waroquiers@skynet.be>
> > Date: Sun, 26 Aug 2018 18:53:58 +0200
> > 
> > +info args [-q] [-t TYPEREGEXP] [NAMEREGEXP]
> > +info functions [-q] [-t TYPEREGEXP] [NAMEREGEXP]
> > +info locals [-q] [-t TYPEREGEXP] [NAMEREGEXP]
> > +info variables [-q] [-t TYPEREGEXP] [NAMEREGEXP]
> > +  These commands can now print only the searched entities
> > +  matching the provided regexp(s), giving a condition
> > +  on the entity names or entity types.
> 
> I'd lose "searched".  How about the following?
> 
>   These commands can now print only the entities whose names and/or
>   types match the specified regular expressions.
> 
> > +                                         The flag -q
> > +  disables printing headers or informations messages.
> 
> "informative messages", I guess?
These are the messages explaining why no entity was printed, e.g
  (gdb) info arg -t xxxx yyyy
  No matching arguments.
  (gdb) info arg -q -t xxxx yyyy
  (gdb) 

  (gdb) info arg -t xxxx yyyy   
  No symbol table info available.
  (gdb) info arg -q -t xxxx yyyy
  (gdb) 

So, what about (like in the texinfo doc):          The flag -q
   disables printing headers or messages explaining why no entities
   have been printed.
?

Philippe


  reply	other threads:[~2018-08-27  4:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-26 16:54 [RFAv2 0/6] info [args|functions|locals|variables] [-q] [-t TYPEREGEXP] [NAMEREGEXP] Philippe Waroquiers
2018-08-26 16:54 ` [RFAv2 3/6] Add [-q] [-t TYPEREGEXP] [NAMEREGEXP] args to info [args|functions|locals|variables] Philippe Waroquiers
2018-09-18 15:52   ` Tom Tromey
2018-09-23 21:34     ` Philippe Waroquiers
2018-08-26 16:54 ` [RFAv2 4/6] Document changes " Philippe Waroquiers
2018-08-26 18:19   ` Eli Zaretskii
2018-08-26 16:54 ` [RFAv2 1/6] New cli-utils.h/.c function extract_info_print_args Philippe Waroquiers
2018-09-18 15:31   ` Tom Tromey
2018-09-23 20:16     ` Philippe Waroquiers
2018-09-24 13:07       ` Tom Tromey
2018-09-25  4:37         ` Philippe Waroquiers
2018-08-26 16:54 ` [RFAv2 2/6] Make struct type_print_options default_ptype_flags non static Philippe Waroquiers
2018-08-26 16:54 ` [RFAv2 6/6] Add a test case for info args|functions|locals|variables [-q] [-t TYPEREGEXP] [NAMEREGEXP] Philippe Waroquiers
2018-08-26 16:54 ` [RFAv2 5/6] Announce changes in NEWS to info [args|functions|locals|variables] Philippe Waroquiers
2018-08-26 18:21   ` Eli Zaretskii
2018-08-27  4:39     ` Philippe Waroquiers [this message]
2018-08-27 14:59       ` Eli Zaretskii
2018-09-06 20:16 ` PING Re: [RFAv2 0/6] info [args|functions|locals|variables] [-q] [-t TYPEREGEXP] [NAMEREGEXP] Philippe Waroquiers
2018-09-13 19:27 ` PING^2 " Philippe Waroquiers

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=1535344760.1438.13.camel@skynet.be \
    --to=philippe.waroquiers@skynet.be \
    --cc=eliz@gnu.org \
    --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