On Fri, Jul 26, 2013 at 04:07:55PM +0400, Pavel Fedin wrote: > Hello! > >> I don't think that's fair, since such apps were designed for the >> Windows console, without being aware of Cygwin's pipe-based ptys. And >> unfortunately that list would be very long anyway: basically anything >> interactive that hasn't been explicitly adapted to Cygwin ptys > > Let me also drop my 5 cents into this... >We should be very careful about this. At least there is one case where >difference between Cygwin console and real Windows console plays a key >role: ncurses. Normal Windows console is very basic and does not >understand 90% of control sequences. As a result, ncurses has been >extended with 'terminal drivers', which redirect certain control >functions to OS (Windows in our case) API calls. Which, of course, >work only with real Windows console.
The "console" that a Cygwin program sees is not just the raw Windows console. Hopefully the Cygwin version of ncurses understands that Cygwin extends the functionality of the console so that a big subset of standard control sequences will just work. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
