From: Yao Qi <qiyaoltc@gmail.com>
To: Tom Tromey <tom@tromey.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] PR python/13598 - add before_prompt event
Date: Sun, 12 Feb 2017 23:02:00 -0000 [thread overview]
Message-ID: <CAH=s-POVou4EXJ7nvvgUUkWNfwOaFnyKRr-gtgokpv4=3W3+8Q@mail.gmail.com> (raw)
In-Reply-To: <87y3xc4u9e.fsf@tromey.com>
On Sat, Feb 11, 2017 at 3:33 PM, Tom Tromey <tom@tromey.com> wrote:
>>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
>
> Tom> This adds an event that is emitted just before GDB presents a prompt
> Tom> to the user. This provides Python code a way to react to whatever
> Tom> changes might have been made by the previous command. For example, in
> Tom> my GUI I use this to track changes to the selected frame and reflect
> Tom> them in the UI.
>
> Tom> Built and regtested on x86-64 Fedora 23.
>
> I'd like to ping this patch again.
>
> I tried the suggested alternate approach, which I mentioned last time I
> pinged. However, that approach did not work out correctly. And, the
> approach taken in this patch is what is used by the TUI to do exactly
> the same thing.
>
> So, I'd like to ask you to please reconsider this.
>
Hi Tom,
I am convinced by your arguments. Your patch is good to me.
--
Yao (齐尧)
next prev parent reply other threads:[~2017-02-12 23:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-21 5:01 Tom Tromey
2016-05-21 6:54 ` Eli Zaretskii
2016-07-22 9:34 ` Phil Muldoon
2016-07-22 10:01 ` Yao Qi
2016-07-22 10:22 ` Matt Rice
2016-07-23 5:00 ` Tom Tromey
2016-08-03 8:33 ` Yao Qi
2016-08-03 16:08 ` Tom Tromey
2016-08-03 16:16 ` Pedro Alves
2016-08-04 20:34 ` Tom Tromey
2016-08-05 17:30 ` Pedro Alves
2016-10-09 17:23 ` Tom Tromey
2016-07-22 13:28 ` Phil Muldoon
2017-02-11 15:33 ` Tom Tromey
2017-02-12 23:02 ` Yao Qi [this message]
2017-02-14 18:03 ` 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='CAH=s-POVou4EXJ7nvvgUUkWNfwOaFnyKRr-gtgokpv4=3W3+8Q@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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