From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7628 invoked by alias); 11 May 2005 06:55:08 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 7584 invoked from network); 11 May 2005 06:55:04 -0000 Received: from unknown (HELO mail.codesourcery.com) (65.74.133.9) by sourceware.org with SMTP; 11 May 2005 06:55:04 -0000 Received: (qmail 25057 invoked from network); 11 May 2005 06:55:03 -0000 Received: from localhost (HELO ?192.168.0.5?) (mitchell@127.0.0.1) by mail.codesourcery.com with SMTP; 11 May 2005 06:55:03 -0000 Message-ID: <4281AC36.7080100@codesourcery.com> Date: Wed, 11 May 2005 06:56:00 -0000 From: Mark Mitchell User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) MIME-Version: 1.0 To: Daniel Jacobowitz CC: Eli Zaretskii , bug-readline@gnu.org, gdb-patches@sources.redhat.com Subject: Re: PATCH: Use getche on Win32 References: <200505092015.j49KFoPw028903@sethra.codesourcery.com> <01c55512$Blat.v2.4$85bf3480@zahav.net.il> <42804E09.9060508@codesourcery.com> <01c55598$Blat.v2.4$baecd3c0@zahav.net.il> <428113E4.9090807@codesourcery.com> <01c5559e$Blat.v2.4$1b76ee60@zahav.net.il> <20050510203127.GA10559@nevyn.them.org> In-Reply-To: <20050510203127.GA10559@nevyn.them.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-05/txt/msg00236.txt.bz2 Daniel Jacobowitz wrote: >>If it's important that the current CVS snapshots are available ASAP >>for MinGW users, even though one cannot interrupt the debuggee with >>Ctrl-C, then I don't mind that you check this into the GDB CVS, >>provided that it will be followed soon by more patches to take care of >>the above issues. Thanks! But ... > I would prefer not to commit patches now that will require followup > patches to change their behavior later; there's not that much of a rush > AFAIK. ... I agree that there's no burning crisis, and I don't want to do something that makes people unhappy. As Daniel says, the Ctrl-C issue is independent of this code, and, as Chris says, it's perfectly possible to capture Ctrl-C under Windows; we just don't want to do it here. What I can do in this context is look at Home/End/Delete/Insert/Arrows. I'll do that and report back. Thanks, -- Mark Mitchell CodeSourcery, LLC mark@codesourcery.com (916) 791-8304