From: Phil Muldoon <pmuldoon@redhat.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] PR python/13598 - add before_prompt event
Date: Fri, 22 Jul 2016 09:34:00 -0000 [thread overview]
Message-ID: <73953d5d-a69c-7b45-15c2-52ae4cfea107@redhat.com> (raw)
In-Reply-To: <1463806850-11001-1-git-send-email-tom@tromey.com>
On 21/05/16 06:00, Tom Tromey wrote:
> This adds an event that is emitted just before GDB presents a prompt
> to the user. This provides Python code a way to react to whatever
> changes might have been made by the previous command. For example, in
> my GUI I use this to track changes to the selected frame and reflect
> them in the UI.
>
> Built and regtested on x86-64 Fedora 23.
>
> 2016-05-20 Tom Tromey <tom@tromey.com>
>
> PR python/13598:
> * python/python.c (gdbpy_before_prompt_hook): Emit before_prompt
> event.
> * python/py-evts.c (gdbpy_initialize_py_events): Add
> before_prompt registry.
> * python/py-events.h (events_object) <before_prompt>: New field.
>
> 2016-05-20 Tom Tromey <tom@tromey.com>
>
> PR python/13598:
> * python.texi (Events In Python): Document events.before_prompt.
>
> 2016-05-20 Tom Tromey <tom@tromey.com>
>
> PR python/13598:
> * gdb.python/py-events.exp: Add before_prompt event tests.
Looks good to me. Apologies for the delay in responding.
Note, I'm not a maintainer, so please wait for their approval. Or
approve it yourself (I think you are still a maintainer!)
Cheers
Phil
next prev parent reply other threads:[~2016-07-22 9:34 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 [this message]
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
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=73953d5d-a69c-7b45-15c2-52ae4cfea107@redhat.com \
--to=pmuldoon@redhat.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