Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!peregrine!imt3b2!seila!don
From: don@seila.UUCP (Don Kossman)
Newsgroups: comp.unix.xenix,comp.sys.ibm.pc
Subject: Re: xenix terminal emulation
Message-ID: <331@seila.UUCP>
Date: Sat, 5-Dec-87 15:44:01 EST
Article-I.D.: seila.331
Posted: Sat Dec  5 15:44:01 1987
Date-Received: Fri, 11-Dec-87 06:03:03 EST
References: <244@ivory.SanDiego.NCR.COM>
Reply-To: don@seila.UUCP (Don Kossman, SEI)
Distribution: na
Organization: SEI Information Technology, LA, CA
Lines: 19
Keywords: TERM, termcap
Summary: set TERM to ansi
Xref: mnetor comp.unix.xenix:1281 comp.sys.ibm.pc:10878

In article <244@ivory.SanDiego.NCR.COM> mike@ivory.UUCP (Michael Lodman) writes:
>I am using an NCR PC8 running Xenix 2.1.3 to talk to other Xenix and
>Unix systems. Cu seems to botch up the screen handling horribly when
>I do this - scrolling doesn't work right and the arrow keys don't work 
>at all.

we use cu all the time to log onto other systems; it doesn't do _any_
translation of keyboard output or incoming sequences.  (except to 
look for "~" escape sequences...)  the only thing that should be
required for full-screen applications running on a remote system to
work correctly is that they understand that you are on a "xenix console";
that is, if they use termcap, the TERM variable should be set to "ansi"
and exported, and there should be such an entry in their termcap file.
(often, logging into a dialup port results in TERM being set to "du"..)

don
-- 
Don Kossman, SEI Information Technology, Los Angeles
usenet: {ccicpg!imt3b2 | peregrine!imt3b2 | sun!tsunama!tsunami}!seila!don