Re: RFC: <Ctrl-C> in the Console Window

Re: RFC: <Ctrl-C> in the Console Window

[Fernando Nasser]

Nicholas_Karagas@cirilium.com wrote:
> 
> I asked about this a while back, and the response I got was to bind that
> particular function to Ctrl-. (period), or something like that.  I did, and
> it works fine for me.  That would keep Ctrl-C open for Windows copy.
> 

We could do that Nicholas, but it wouldn't solve the problem.
these users do not read any documentation, they just try to do what
they are used to in the command line version (gdb -nw).

As soon as <Ctrl-C> as they notice that does not work hey immediately file a problem
report, call support, send e-mail, keep arguing that they prefer this.

Maybe I could do this binding anyway, so at least I have something for them
when they call.

Or maybe add the <Cntl-C> preference.  Turned off by default, but if the user
so desires, he/she can change it.

I am sort of flip-flopping on this issue, isn't it?  I guess I must sleep over it
and think about what you guys said and come up with something that makes sense.
(Keith warned me :-)

-- 
Fernando Nasser
Red Hat - Toronto                       E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9

RFC: <Ctrl-C> in the Console Window

[Fernando Nasser]

Some user's, instead of clicking the cute red STOP button, insist in
issuing a <Ctrl-C> in the poor simulated GDB console (the Console Window).

I have been asked so many times this same question that, despite the fact
that I would like to tell them to use "gdb -nw" if they want a real console,
I am felling compelled to add this feature.

If there is no objections, I will bind <Ctrl-C> to (something that calls)
gdbtk_stop.

Any reason why I should not do that?


-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9