Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com From: Chris Faylor Date: Mon, 25 Sep 2000 11:54:12 -0400 To: Cygwin Subject: Re: Can't abort command line with Ctrl-C anymore... Message-ID: <20000925115412.A9979@cygnus.com> Reply-To: cygwin@sources.redhat.com Mail-Followup-To: Cygwin References: <028201c02675$1b5ef150$db41480c@hxzcw> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <028201c02675$1b5ef150$db41480c@hxzcw>; from johnston.p@worldnet.att.net on Sun, Sep 24, 2000 at 03:16:35PM -0700 On Sun, Sep 24, 2000 at 03:16:35PM -0700, Paul Johnston wrote: >Hi, I've just upgraded from B20 to net release 1.1.4 (latest, as of today). >Nice install! Anyway, when I type a command ctrl-c does not abort it. >Ctrl-C still works to interrupt a running process, but I can't bail out of a >command without using the backspace key. Is this a setting or has the >behavior of bash changed? I'm on NT4. It's a bug in Cygwin 1.1.4. This has been mentioned many times. Check the mailing list archives. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com