Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: pln@egret1.stanford.edu (Patrick L. Nolan)
Newsgroups: comp.sys.sun
Subject: bug in 4.1.1 terminfo?
Keywords: Miscellaneous
Message-ID: <2460@brchh104.bnr.ca>
Date: 17 Apr 91 01:00:00 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 16
Approved: Sun-Spots@rice.edu
X-Original-Date: 10 Apr 91 21:40:12 GMT
X-Sun-Spots-Digest: Volume 10, Issue 81, message 17
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

We upgraded to SunOS 4.1.1 a little while ago, and a user came in with a
problem that hadn't been seen before.  He uses vi on a vt220 terminal, and
the arrow keys quit working.  I checked the terminfo entries and found
that the codes gived for the arrow keys (kcub1, kcuf1, kcuu1, and kcud1)
were wrong for the vt220 entry.  According to /usr/5bin/infocmp they were
\E[A etc., while they should be \EOA etc.

The funny thing is that this holds only for the vt220 entry, not 
vt220-js, vt220-w, or any of the vt200 family.

Has anyone else seen this?  Is this a new feature in 4.1.1?

*   Patrick L. Nolan            (415)723-0133                 *
*   W. W. Hansen Experimental Physics Laboratory (HEPL)       * 
*   Stanford University                                       *
*   Bitnet: PLN@SLACVM    Internet: pln@egret1.stanford.edu   *