Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!snorkelwacker!usc!pollux.usc.edu!papa
From: papa@pollux.usc.edu (Marco Papa)
Newsgroups: comp.sys.amiga.tech
Subject: Re: JRComm (Was Re: AMIGA too slow for speeds higher than 9600 Baud? HELP!)
Message-ID: <24552@usc.edu>
Date: 7 May 90 18:55:35 GMT
References: <1494@lpami.wimsey.bc.ca>
Sender: news@usc.edu
Organization: Felsina Software, Los Angeles, CA
Lines: 30

In article <1494@lpami.wimsey.bc.ca> lphillips@lpami.wimsey.bc.ca (Larry Phillips) writes:
>In <1366@faatcrl.UUCP>, jprad@faatcrl.UUCP (Jack Radigan) writes:
>>  Hmmm, hadn't thought of it that way before.  24?  You're fogetting the status
>>line....
>
>Is the status line part of the normal screen as seen by the host? ie. does the
>host explicitly write out the status line itself in the same way that it writes
>out the rest of the lines? If not, I would not consider it part of the
>'screen'. You will, of course, have to have room for it there, but for
>communication purposes, it doesn't exist, so you only allow the host to muck
>with a 24 line screen. If it is treated as a normal line by the host, then
>ignore the above comments.

Of course Larry is the one that's right.  VT100s do not have a status line
that is addressable from the host. Therefore they are simply 80x24 or
132x24 terminals.  Same for VT52.  The H19, though has a status line, but
it has its own private sequences to write on it.

Termcap and Terminfo have no concept of a status line.

As such, 'status lines' are NOT part of a screen. They CAN'T be scrolled
with the rest of the screen.

ANSI doesn't have a concept of status line AT ALL, so forget about status lines
in general.

-- Marco
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
"Xerox sues somebody for copying?" -- David Letterman
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=