Alex Dupre wrote: > Wednesday, July 10, 2002, 10:22:22 PM, you wrote: > TL> Sounds like Cygwin's terminal program fails to correctly implement > TL> the ANSI 3.64 standard. Could you use an ANSI 3.64 standard terminal, > TL> instead? Windows Telnet is standards compliant, for example. > > I can use other terminals, usually from windows machines I use putty > that works good, but I'd like a working cygwin, too.
Cygwin problem. I'd like a working Microsoft Windows. 8-). > Thanks for your suggestions. I tried to replace the cygwin termcap > entry with the one included in cygwin and many problems disappeared, > but not all. > > TL> Actually, if you do a search for: > > TL> termcap entry test program > > TL> You should be able to quickly identify what's wrong with your > TL> termcap entry, or if it's actually another Cygwin bug. > > Can you give me more details on this test program, pls? I couldn't > find it. It's included in the "ncurses" package. There's also one called "aC" that's included with the O'Reilly "Termcap and Terminfo" book, and there are three or four of them in the comp.unix.sources archives (if I remember correctly, Archive #27 has one of them). Basically, you run it, and then step through it, and it tells you should see, and if you don't see what it tells you you should see, then you correct your termcap entry so that the output becomes more correct. It will test things like "AM" and "AW", etc., which are common places implementations of termcap entries are broken. -- TErry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
