From: Pavel Fedin <p.fedin@samsung.com>
To: cygwin@cygwin.com
Subject: RE: BLODA extension: console interoperability
Date: Mon, 29 Jul 2013 09:06:00 -0000 [thread overview]
Message-ID: <003301ce8c1b$397afc50$ac70f4f0$%fedin@samsung.com> (raw)
In-Reply-To: <20130726152944.GD4495@ednor.casa.cgf.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
prev parent reply other threads:[~2013-07-29 5:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 23:07 Warren Young
2013-07-26 2:50 ` Larry Hall (Cygwin)
2013-07-26 4:44 ` Warren Young
2013-07-26 5:02 ` Larry Hall (Cygwin)
2013-07-26 5:20 ` Andy Koppe
2013-07-26 6:13 ` Warren Young
2013-07-26 6:44 ` Christopher Faylor
2013-07-26 14:59 ` Pavel Fedin
2013-07-26 16:22 ` Christopher Faylor
2013-07-27 3:18 ` Charles Wilson
2013-07-29 9:06 ` Pavel Fedin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='003301ce8c1b$397afc50$ac70f4f0$%fedin@samsung.com' \
--to=p.fedin@samsung.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).