X-Spam-Check-By: sourceware.org
Message-ID: <44608723.4000804@byu.net>
Date: Tue, 09 May 2006 06:12:19 -0600
From: Eric Blake <ebb9 AT byu DOT net>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
CC: jlange6648 AT gmail DOT com
Subject: Re: terminal escape codes
References: <d62889820605051037l48fa4e63qa6975b9423bba101 AT mail DOT gmail DOT com> <445B9333 DOT 6090109 AT cygwin DOT com> <d62889820605051110u1327c9f6i98686cb42c927d6e AT mail DOT gmail DOT com> <e3hhha$6r0$1 AT sea DOT gmane DOT org> <Pine DOT GSO DOT 4 DOT 63 DOT 0605081106300 DOT 24916 AT access1 DOT cims DOT nyu DOT edu> <e3otnf$ko5$1 AT sea DOT gmane DOT org> <d62889820605090501r3e920107hd835862e1a5f5f2 AT mail DOT gmail DOT com>
In-Reply-To: <d62889820605090501r3e920107hd835862e1a5f5f2@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Jeff Lange on 5/9/2006 6:01 AM:
> We attempted to use rxvt, but the issue is that the application that
> is running uses F key's that don't appear to map correctly when using
> rxvt, but do work when using the normal cygwin shell.
> 
> The root of the question is though, why doesn't the standard shell
> handle the ESC(B code correctly?  This is a bug is it not?

The cygwin terminal in a cmd.com window is NOT a VT220 emulator.  You are
using a different terminal that understands a different set (read subset)
of escape codes.  The only bug here is that you are expecting cygwin to
behave the same on all escape sequences as some other terminal, when
escape sequences are not standardized (well, except for the ANSI ESC[
sequences).  The reason that ESC(B prints B is that ESC( is an unknown
escape sequence, so those two characters are silently discarded, leaving
the B to display on the screen.

That said, it is possible to see if you can implement the missing escape
codes; see fhandler_console::write in
http://cygwin.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/fhandler_console.cc?rev=1.162&content-type=text/x-cvsweb-markup&cvsroot=src
for the current code that does escape sequence handling when TERM is
cygwin.  http://cygwin.com/acronyms/#PTC

- --
Life is short - so eat dessert first!

Eric Blake             ebb9 AT byu DOT net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEYIch84KuGfSFAYARApZbAJ9NVo0TQ3KMl/r4BhQKfYown6QpoACg1T9/
T9tlZ5RSIlMQWbJ+mr/rIGc=
=90mM
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/