From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Phil Muldoon <pmuldoon@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [patch][python] 5 of 5 - Frame filter documentation changes
Date: Wed, 05 Dec 2012 19:11:00 -0000 [thread overview]
Message-ID: <87boe8s49y.fsf@fleche.redhat.com> (raw)
In-Reply-To: <83boeet4wh.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 01 Dec 2012 12:58:54 +0200")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
Eli> So in CLI, each filter can be enabled and disabled individually, but
Eli> in MI they can only be enabled en masse, and cannot be disabled? is
Eli> that a good idea?
In MI it is fine. It is no extra effort for an MI client to request
unfiltered output on each invocation it cares to.
The reason for the enablement command for MI is just so that clients
don't get filtered output without expecting it. This would work ok --
the output is backward compatible -- but could be surprising to users.
An MI client could disable filters individually. The commands are
always there.
Tom
next prev parent reply other threads:[~2012-12-05 19:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 14:32 Phil Muldoon
2012-12-01 10:59 ` Eli Zaretskii
2012-12-05 19:11 ` Tom Tromey [this message]
2012-12-07 14:35 ` Phil Muldoon
2012-12-07 15:04 ` Eli Zaretskii
2012-12-07 15:34 ` Phil Muldoon
2012-12-07 15:54 ` Eli Zaretskii
2012-12-05 20:49 ` Tom Tromey
2012-12-07 14:55 ` Phil Muldoon
2013-03-11 22:14 Phil Muldoon
2013-03-12 17:24 ` Eli Zaretskii
2013-03-22 19:54 ` Tom Tromey
2013-04-19 14:24 ` Phil Muldoon
2013-04-22 17:03 Phil Muldoon
2013-04-26 11:54 ` Tom Tromey
2013-05-10 10:52 ` Phil Muldoon
2013-05-06 8:24 Phil Muldoon
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=87boe8s49y.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@redhat.com \
/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