Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: John Pye <john.pye@anu.edu.au>
To: Joel Brobecker <brobecker@adacore.com>,
	  Andrew STUBBS <andrew.stubbs@st.com>,
	  gdb@sourceware.org
Subject: Re: usability: exiting from GDB
Date: Thu, 30 Nov 2006 03:59:00 -0000	[thread overview]
Message-ID: <456E5704.8060102@anu.edu.au> (raw)
In-Reply-To: <20061129133748.GC28834@nevyn.them.org>

Hi again

I have been reading the thread, yes. But my last post wasn't expressed
very clearly, sorry.

The ctrl-D behaviour is what I would prefer, certainly, and this would
be more shell-like. But I don't like the confirmation question "Exit
anyway?".

The hook-quit thing does turn off the confirmation in the case of the
"q" command, but *does not* work for the ctrl-D exit method.

I guess the main thing is to get the ctrl-D functionality right.
Presuming that others agree that this change would be desirable?

I find the ctrl-C behaviour unhelpful (ie suggesting I quit instead of
asking me if I'd like to go ahead and do it) but it's not important really.

Cheers

Daniel Jacobowitz wrote:
> On Wed, Nov 29, 2006 at 06:16:22PM +1100, John Pye wrote:
>   
>> The whole thing is that gdb is like a shell. And shells can be exited by
>> typing ctrl-D. It's about consistency with other similar tools. That's
>> my feeling, anyway.
>>     
>
> Did you read the previous replies to your message?  Shells don't exit
> when you press C-c and it would be upsetting to at least some users if
> GDB did; it does exit if you press C-d at a prompt.
>
>   


Daniel Jacobowitz wrote:
> On Wed, Nov 29, 2006 at 06:16:22PM +1100, John Pye wrote:
>   
>> The whole thing is that gdb is like a shell. And shells can be exited by
>> typing ctrl-D. It's about consistency with other similar tools. That's
>> my feeling, anyway.
>>     
>
> Did you read the previous replies to your message?  Shells don't exit
> when you press C-c and it would be upsetting to at least some users if
> GDB did; it does exit if you press C-d at a prompt.
>
>   


  parent reply	other threads:[~2006-11-30  3:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-27  5:38 John Pye
2006-11-27  6:50 ` Eli Zaretskii
2006-11-27  7:43   ` John Pye
2006-11-27 13:42     ` Eli Zaretskii
2006-11-27 13:51 ` Daniel Jacobowitz
2006-11-27 14:46 ` Andrew STUBBS
2006-11-29  3:27   ` John Pye
2006-11-29  4:50     ` Daniel Jacobowitz
2006-11-29  5:04     ` Joel Brobecker
2006-11-29  7:16       ` John Pye
2006-11-29 13:38         ` Daniel Jacobowitz
2006-11-29 14:12           ` Bob Rossi
2006-11-30  4:01             ` John Pye
2006-11-30  8:32               ` Brian Dessent
2006-11-30 11:58                 ` John Pye
2006-11-30 12:34                   ` Andrew STUBBS
2006-11-30  3:59           ` John Pye [this message]
2006-11-30 10:10             ` Andrew STUBBS
2006-11-30 11:51               ` John Pye
2006-11-30 21:49             ` Michael Snyder

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=456E5704.8060102@anu.edu.au \
    --to=john.pye@anu.edu.au \
    --cc=andrew.stubbs@st.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    /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