From: Eli Zaretskii <eliz@gnu.org>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC 3/5] Add [-q] [-t TYPEREGEXP] [NAMEREGEXP] args to info [args|functions|locals|variables]
Date: Mon, 02 Jul 2018 15:06:00 -0000 [thread overview]
Message-ID: <831sclllsu.fsf@gnu.org> (raw)
In-Reply-To: <20180701210734.3793-4-philippe.waroquiers@skynet.be> (message from Philippe Waroquiers on Sun, 1 Jul 2018 23:07:32 +0200)
> From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
> Cc: Philippe Waroquiers <philippe.waroquiers@skynet.be>
> Date: Sun, 1 Jul 2018 23:07:32 +0200
>
> + if (!cb_data.values_printed && !quiet)
> + {
> + if (regexp == NULL && t_regexp == NULL)
> + fprintf_filtered (stream, _("No locals.\n"));
> + else
> + fprintf_filtered (stream, _("No matching locals.\n"));
> + }
I believe this is not our indentation style.
next prev parent reply other threads:[~2018-07-02 15:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-01 21:07 [RFC 0/5] info [args|functions|locals|variables] [-q] [-t TYPEREGEXP] [NAMEREGEXP] Philippe Waroquiers
2018-07-01 21:07 ` [RFC 1/5] New cli-utils.h/.c function extract_info_print_args Philippe Waroquiers
2018-07-01 21:07 ` [RFC 5/5] Announce changes in NEWS to info [args|functions|locals|variables] Philippe Waroquiers
2018-07-02 14:51 ` Eli Zaretskii
2018-07-01 21:07 ` [RFC 3/5] Add [-q] [-t TYPEREGEXP] [NAMEREGEXP] args " Philippe Waroquiers
2018-07-02 15:06 ` Eli Zaretskii [this message]
2018-07-01 21:07 ` [RFC 2/5] Make struct type_print_options default_ptype_flags non static Philippe Waroquiers
2018-07-01 21:07 ` [RFC 4/5] Document changes to info [args|functions|locals|variables] Philippe Waroquiers
2018-07-02 15:02 ` Eli Zaretskii
2018-07-02 20:46 ` Philippe Waroquiers
2018-07-04 16:44 ` Eli Zaretskii
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=831sclllsu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=philippe.waroquiers@skynet.be \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).