From: Tom Tromey <tromey@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/6] attach to command_option-changed observer.
Date: Fri, 27 Jul 2012 17:44:00 -0000 [thread overview]
Message-ID: <87wr1payl8.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1343402543-665-3-git-send-email-yao@codesourcery.com> (Yao Qi's message of "Fri, 27 Jul 2012 23:22:19 +0800")
>>>>> "Yao" == Yao Qi <yao@codesourcery.com> writes:
Yao> This patch is to attach function 'mi_command_option_changed' to
Yao> observer 'command_option_changed', so that a MI notification
Yao> "=option-changed" is sent to MI frontend. If the command option
Yao> change is requested from MI, the notification is suppressed.
It occurs to me now that, when we had the naming discussion for the
Python feature related to set/show, we ended up with the name
"parameter" rather than "option" or "variable". Perhaps it would be
best if MI adopted this same naming convention.
Tom
next prev parent reply other threads:[~2012-07-27 17:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 15:23 [RCF 0/6 V2] MI notification of command option change Yao Qi
2012-07-27 15:23 ` [PATCH 1/6] new observer command_option_changed Yao Qi
2012-07-27 17:56 ` Tom Tromey
2012-07-27 15:23 ` [PATCH 4/6] notify in boolean_cmd and circular-trace-buffer Yao Qi
2012-07-27 15:23 ` [PATCH 5/6] notify in string_cmd and trace-notes Yao Qi
2012-07-27 15:23 ` [PATCH 2/6] attach to command_option-changed observer Yao Qi
2012-07-27 17:20 ` Tom Tromey
2012-07-27 17:44 ` Tom Tromey [this message]
2012-07-27 15:23 ` [PATCH 6/6] code indentation Yao Qi
2012-07-27 15:23 ` [PATCH 3/6] notify in enum_cmd and scheduler-locking Yao Qi
2012-07-27 17:07 ` [RCF 0/6 V2] MI notification of command option change Tom Tromey
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=87wr1payl8.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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