Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID: <009801c285d6$3d8001d0$b001a8c0@coosbayreza>
From: "Reza Roodsari" <rroodsari AT osatechnologies DOT com>
To: <cygwin AT cygwin DOT com>
Subject: Problem with function keys codes with vt100 emulation
Date: Wed, 6 Nov 2002 12:51:12 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300

Hi I've spent two days investigating this and sorry if this has been
answered already.  I was not able to find any references.

The problem I have is that the cygwin terminal window which runs the bash
shell is generating the wrong key codes when function keys, such as f1, f2,
etc, are pressed.

Ordinarily the terminal starts out with TERM=cygwin.  cygwin terminal
emulation correctly produces the \E[[A for f1, \E[[B for f2, and other
function keys.  I then change TERM to vt100 and expect to get \EOP for f1,
\EOQ for f2, etc but still get the old cygwin mode key codes.

Looking into the /etc/termcap file shows that vt100 terminal mode should
produce \EOP for f1.

I am not exactly sure what the problem is but when I run captoinfo on
/etc/termcap I get a bunch of errors reported.  This may be an unrelated
problem.

My version of cygwin is 1.3.12, dated 2002-07-06.

I would like to know if this is a bug and if so whether there is a fix.

Any help would be appreciated.

Thanks in advance.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/