This is the mail archive of the
mailing list for the Cygwin project.
Re: BLODA extension: console interoperability
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 26 Jul 2013 11:29:44 -0400
- Subject: Re: BLODA extension: console interoperability
- References: <51F1A863 dot 8060403 at etr-usa dot com> <51F1AF90 dot 3080409 at cygwin dot com> <51F1F7B4 dot 4060202 at etr-usa dot com> <CAHWeT-bBvWyv0dzFkwbgyKJKuNyaVY85ZBkksCC-Qs_dZ6H+GA at mail dot gmail dot com> <003601ce89f8$c3845f10$4a8d1d30$%fedin at samsung dot com>
- Reply-to: cygwin at cygwin dot com
On Fri, Jul 26, 2013 at 04:07:55PM +0400, Pavel Fedin wrote:
>> 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.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple