From: Jim Ingham <jingham@apple.com>
To: <Nicholas_Karagas@cirilium.com>, Keith Seitz <kseitz@firetalk.com>
Cc: <insight@sourceware.cygnus.com>
Subject: Re: prompt in console window
Date: Thu, 15 Jun 2000 10:35:00 -0000 [thread overview]
Message-ID: <B56E61C9.1323%jingham@apple.com> (raw)
In-Reply-To: <OF0F0BE1D5.6BBF9C46-ON072568FF.005D75CA@cirilium.com>
Nicholas,
Control-C actually means copy in the console window, as God intended :-)
However, wiring up the stop button so that it would also interrupt macros
might not be a bad idea... Or using Control-. or escape are other good
options.
Remember also that in most GUI applications, Control-C does not generate a
SIGINT, since the GUI wants to handle all the key sequences itself. So to
interrupt a macro while it is running, gdb would have to be giving control
periodically back to the GUI. Don't know whether this is true or not...
Jim
> Hmm... perhaps I can ask an easier question. The only reason that I wanted
> to get the prompt_for_continue prompt back was that I wanted a way to stop
> a gdb macro (the kind that are defined in the .gdbinit file) that had
> started running, in case it was taking too long and I didn't care about the
> rest of the output. With the command-line gdb, you could type Ctrl-C at
> that prompt to stop whatever was running, including a macro. Would it be
> easier (and more helpful to the rest of the world) to get Ctrl-C working in
> the console window instead of the unnecessary prompt?
next prev parent reply other threads:[~2000-06-15 10:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-15 10:11 Nicholas_Karagas
2000-06-15 10:35 ` Jim Ingham [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-14 13:02 Nicholas_Karagas
2000-06-15 6:11 ` Keith Seitz
2000-06-15 10:29 ` Jim Ingham
2000-06-15 10:42 ` Keith Seitz
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=B56E61C9.1323%jingham@apple.com \
--to=jingham@apple.com \
--cc=Nicholas_Karagas@cirilium.com \
--cc=insight@sourceware.cygnus.com \
--cc=kseitz@firetalk.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).