getc() problem with Cygwin v1.0
Fri Jan 14 22:35:00 GMT 2000
Earnie Boyd writes...
>Hmm... I just did `export TERM=ansi' and I can still do the backspace. What
>happens if you do Ctrl-H instead of the Backspace key? Is it possible that
>your Backspace key is mapped to be the Delete key? BTW, my CYGWIN variable
>isn't set at all.
Chris Faylor writes...
>I thought that I'd responded to this already but I can't find it in my mail
>There is a bug in the handling of "cooked" mode in cygwin 1.0 iff you are
>using CYGWIN=tty. There is no workaround other than to download a snapshot.
OK, now we're talking. I unset my CYGWIN variable and now everything
Thanks everyone for your help with this one.
>From Eric Fifer...
>I'm not sure this is related, but I posted about something
>similar a few weeks back (and had no responses). I'm not
>running v1.0, right now I'm running the 2000/01/05 snapshot
>and the following is still true ...
>Subject: line editing not working with rxvt and recent cygwin snapshots
>Line editing (erase/kill) isn't working within rxvt. I'm not
>sure why, but characters are being processed immediately.
>It's easy to demonstrate, start up "cat" reading from stdin and then
>just type "abc ENTER".
>In the normal console you'll see:
> bash$ cat
> bash$ cat
>With my old b20.1 setup, rxvt and line editing works fine.
>For the test, I forced my stty settings to be identical
>on both ttys. And CYGWIN does set "tty".
Thanks for the post. I would suggest un-setting your CYGWIN=tty
variable and see if you still have the problem.
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org
More information about the Cygwin