From: Tom Tromey <tromey@redhat.com>
To: Stephane Carrez <stephane.carrez@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH]: Fix gdb's prompt for continue in TUI SingleKey mode
Date: Tue, 13 Nov 2012 16:33:00 -0000 [thread overview]
Message-ID: <87r4nx8nut.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAJJuuYr=Y5c9W1HkN3ywk8O+zkFdvVof6tUNrXW-J-GkJi9Dkw@mail.gmail.com> (Stephane Carrez's message of "Tue, 13 Nov 2012 08:36:40 +0100")
>>>>> "Stephane" == Stephane Carrez <stephane.carrez@gmail.com> writes:
Stephane> The problem is that the TUI must know that a gdb command is
Stephane> being executed. This way, if it interacts with the user, it
Stephane> has to be in the mode where a prompt is displayed.
Stephane> If we add some boolean predicate function that tells us we are
Stephane> executing some command (whatever the command, a user, a set, a
Stephane> show, ...) this would be fine for me. Some kind of
Stephane> 'is_executing_command_p'.
Something like this would be fine by me.
Tom
prev parent reply other threads:[~2012-11-13 16:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 13:25 Stephane Carrez
2012-11-12 15:44 ` Tom Tromey
2012-11-13 7:36 ` Stephane Carrez
2012-11-13 16:33 ` Tom Tromey [this message]
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=87r4nx8nut.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=stephane.carrez@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