Re: Win9X Ver 4.10: bash Ctrl-C no echo problem.

Re: Win9X Ver 4.10: bash Ctrl-C no echo problem.

[Earnie Boyd]

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@wmsgaming.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@sourceware.cygnus.com
> 

__________________________________________________
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Win9X Ver 4.10: bash Ctrl-C no echo problem.

[Chris Faylor]

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@wmsgaming.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@sourceware.cygnus.com

Re: Win9X Ver 4.10: bash Ctrl-C no echo problem.

[Julian Kinraid]

Tom Weichmann 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
> 
> I tried to reproduce this effect described above, and can not get the
> same results.  I am running on Win98 4.10 build 2222 (Win98 se).
> I wonder if this is some problem with Win98 which was fixed in the
> second edition?!?

I tried it out, and had the problem, and I'm using the original Win98
release.

Julian Kinraid

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Win9X Ver 4.10: bash Ctrl-C no echo problem.

[Tom Weichmann]

> 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


I tried to reproduce this effect described above, and can not get the 
same results.  I am running on Win98 4.10 build 2222 (Win98 se).  
I wonder if this is some problem with Win98 which was fixed in the 
second edition?!?

Thank You,



Tom Weichmann

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Win9X Ver 4.10: bash Ctrl-C no echo problem.

[Diel, Robert]

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@sourceware.cygnus.com