From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: cygwin@cygwin.com
Subject: Re: BLODA extension: console interoperability
Date: Sat, 27 Jul 2013 03:18:00 -0000 [thread overview]
Message-ID: <51F32DE4.3090108@cwilson.fastmail.fm> (raw)
In-Reply-To: <20130726152944.GD4495@ednor.casa.cgf.cx>
On 7/26/2013 11:29 AM, Christopher Faylor wrote:
> On Fri, Jul 26, 2013 at 04:07:55PM +0400, Pavel Fedin wrote:
>> 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.
cygwin-ncurses does not do any of the stuff that Pavel described. It
treats the cygwin terminal just as described by $TERM (which, if
TERM=cygwin, uses the terminfo definition we've painstakingly created
over the years) -- and so takes advantage of the "gloss" that cygwin
places over the plain console.
OTOH, if TERM=xterm, for instance, then it just uses the xterm terminfo.
--
Chuck
--
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
next prev parent reply other threads:[~2013-07-27 2:18 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 [this message]
2013-07-29 9:06 ` Pavel Fedin
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=51F32DE4.3090108@cwilson.fastmail.fm \
--to=cygwin@cwilson.fastmail.fm \
--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).