From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: Matt Rice <ratmice@gmail.com>, Yao Qi <qiyaoltc@gmail.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] PR python/13598 - add before_prompt event
Date: Fri, 05 Aug 2016 17:30:00 -0000 [thread overview]
Message-ID: <bc9c674a-5c68-53f9-c351-6d4f8e1da4b9@redhat.com> (raw)
In-Reply-To: <8737mkz325.fsf@tromey.com>
On 08/04/2016 09:34 PM, Tom Tromey wrote:
>>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
>
>>> Right now my GUI uses this event to react appropriately when the user
>>> types "up" or "down".
>
> Pedro> The TUI uses this approach too nowadays.
>
> Thanks for mentioning that. I think it's another argument for accepting
> this patch.
I do agree that an event for user-selected frame changes might be nice.
However, I'm fine with the approach in this patch as well, because
I'm sure that even if a frame-change event is added in the future,
a before_prompt event can still find other uses.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-08-05 17:30 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 [this message]
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=bc9c674a-5c68-53f9-c351-6d4f8e1da4b9@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.com \
--cc=ratmice@gmail.com \
--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