This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: BLODA extension: console interoperability
- From: Pavel Fedin <p dot fedin at samsung dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 29 Jul 2013 09:19:38 +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> <20130726152944 dot GD4495 at ednor dot casa dot cgf dot cx>
Hello!
> 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.
I know this. But i was talking about running MinGW (i. e. Windows native)
software with MinGW nCurses under such a console.
I believe, for case Cygwin software cygwin.dll fixes this up and interprets
missing ESC sequences. But if we run MinGW program from within this console,
it won't have this functionality and will talk to the console directly.
In other case, we might run this program from within MinTTY. As far as i
can understand, MinTTY is a complete terminal emulator which understands all
ESC sequences by itself. In this case MinGW program will need to use ESC
sequences too. But if MinGW program will think that it's running on a real
Windows console, it will try to use Windows API, which obviously will not
work.
I agree that this is kind of corner case, but it's still there, if we talk
about interoperability.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
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