Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.unix.questions
Subject: Re: Multiscreen on Unix
Message-ID: <7173@mimsy.UUCP>
Date: Tue, 23-Jun-87 10:32:17 EDT
Article-I.D.: mimsy.7173
Posted: Tue Jun 23 10:32:17 1987
Date-Received: Thu, 25-Jun-87 03:17:09 EDT
References: <910@minnow.UUCP> <5942@brl-smoke.ARPA> <103@rb442.UUCP> <2690@ncoast.UUCP>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 21

>As quoted from <699@mrstve.UUCP> by rjk@mrstve.UUCP (Richard Kuhns):
>+---------------
>| I didn't mean to emulate the entire curses library -- I just want to
>| keep track of what is on 1 or more virtual screens....
>+---------------

In article <2690@ncoast.UUCP> allbery@ncoast.UUCP (Brandon Allbery) writes:
>Ah, but it does!  How is the protocol module to know that ESC [ is a lead-in
>for an escape sequence on ANSI terminals and "position cursor to row" (may
>be column?) on Wyse 50's?

I am not sure I should be feeding this discussion, but I would point
out that this is not necessary.  Any screen management system, whether
user or kernel based, can provide a virtual terminal with a private
termcap to each separate screen or window.  The protocol module could
interpret ANSI sequences, while the ultimate screen refersh is done
with Wyse sequences.  (The Maryland Window System, which was all user
code, worked this way.)
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690)
Domain:	chris@mimsy.umd.edu	Path:	seismo!mimsy!chris