From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] PR python/13598 - add before_prompt event
Date: Sat, 21 May 2016 06:54:00 -0000 [thread overview]
Message-ID: <83vb277vge.fsf@gnu.org> (raw)
In-Reply-To: <1463806850-11001-1-git-send-email-tom@tromey.com> (message from Tom Tromey on Fri, 20 May 2016 23:00:50 -0600)
> From: Tom Tromey <tom@tromey.com>
> Cc: Tom Tromey <tom@tromey.com>
> Date: Fri, 20 May 2016 23:00:50 -0600
>
> 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.
OK for the documentation part.
Thanks.
next prev parent reply other threads:[~2016-05-21 6:54 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 [this message]
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
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=83vb277vge.fsf@gnu.org \
--to=eliz@gnu.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).