Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Tue, 9 May 2000 12:09:30 -0400
To: "'cygwin AT sourceware DOT cygnus DOT com'" <cygwin AT sourceware DOT cygnus DOT com>
Subject: Re: Win9X Ver 4.10:  bash Ctrl-C no echo problem.
Message-ID: <20000509120930.B6339@cygnus.com>
Reply-To: cygwin AT sourceware DOT cygnus DOT com
Mail-Followup-To: cgf AT cygnus DOT com,
	"'cygwin AT sourceware DOT cygnus DOT com'" <cygwin AT sourceware DOT cygnus DOT com>
References: <20000509152901 DOT 18496 DOT qmail AT web111 DOT yahoomail DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.12i
In-Reply-To: <20000509152901.18496.qmail@web111.yahoomail.com>; from earnie_boyd@yahoo.com on Tue, May 09, 2000 at 08:29:01AM -0700

It sounds like we need cygcheck output for this.

cygcheck -r -s -v

cgf

On Tue, May 09, 2000 at 08:29:01AM -0700, Earnie Boyd wrote:
>I've just tried this and find that it works properly.  I'm using the original
>net release 1.1.0 2000-03-01 with CYGWIN=nontsec.
>
>Earnie.
>--- "Diel, Robert" <RDiel AT wmsgaming DOT com> wrote:
>> To whom it may concern,
>> 	I checked the FAQ on this one, and a bit of the Mailing List and
>> came up with nothing.  It seems if I have bash in 'set -o vi' mode and hit
>> the ctrl-c after after 'k'ing back through commands I lose echo.  This is
>> not reported by stty, stty still believes that all the -echo's are still
>> around, and 'stty sane' does nothing to help the situation.  The other weird
>> thing is that echo sort of comes back on each command line when the
>> backspace keyboard, but then is lost on the next line.  Occassionally the
>> command prompt is also not echoed.  To reproduce this problem just type the
>> following:
>> 
>> # set -o vi
>> # ls
>> # <ESC>-k
>> # ctrl-C
>> 
>> every command typed at the prompt, and even maybe the prompt will disappear.
>> Good luck and thank you for your time,
>> Robert

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com