Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: Pedro Alves <palves@redhat.com>,  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: Sun, 09 Oct 2016 17:23:00 -0000	[thread overview]
Message-ID: <87pon9cu7n.fsf@tromey.com> (raw)
In-Reply-To: <8737mkz325.fsf@tromey.com> (Tom Tromey's message of "Thu, 04 Aug	2016 14:34:10 -0600")

>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:

Pedro> The TUI uses this approach too nowadays.

Tom> Thanks for mentioning that.  I think it's another argument for accepting
Tom> this patch.

Hi!

I'd like this patch to be reconsidered for approval.

Today I tried rewriting this patch to use the new
user_selected_context_changed observer.

However, this runs into problems.

First, this observer is not notified when a breakpoint is hit.
It seems to me like it ought to be.

One idea is to attach a second handler to the "stop" event.  However,
stop events are fired too often -- in particular if you set a breakpoint
and put commands like this:

  silent
  cont

... the "stop" event will be fired for every breakpoint hit -- even
though from a "user" point of view this isn't stopping.

Given that the TUI uses the approach given in the before_prompt patch,
and given that there haven't been any negative comments on the patch
itself, I'd like to suggest approving this patch.  As noted elsewhere,
acceptance of this patch does not prevent inclusion of any future event.

thanks,
Tom


  parent reply	other threads:[~2016-10-09 17:23 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 [this message]
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=87pon9cu7n.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=qiyaoltc@gmail.com \
    --cc=ratmice@gmail.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