Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: DEBUG and Screen ManaGement
Message-ID: <9074@ucbvax.ARPA>
Date: Mon, 15-Jul-85 14:28:04 EDT
Article-I.D.: ucbvax.9074
Posted: Mon Jul 15 14:28:04 1985
Date-Received: Wed, 17-Jul-85 06:24:46 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 21

From: Provan@LLL-MFE.ARPA


At DECUS, someone mentioned that "DEBUG uses SMG".  I was puzzled about
this at the time, especially since the SMG person there concurred, and
I finally got a chancce to investigate.  Unless I'm doing something
radically wrong, I see absolutely *no* evidence that DEBUG uses the
screen management package in any way.  The only thing I can see that may
have fooled someone is that DEBUG does detect the ANSI bit being set
and sends ANSI sequences to it.  (Setting a local terminal type will set
the ANSI bit if it's set in the definition.)  I don't know where it's
getting its sequences, either, but even they don't appear to be coming
from SMG, since SMG uses $[<mumble>H for cursor addressing and DEBUG
uses $[<mumble>f.

For the past two DECI, people have been saying "only a few utilities
use SMG."  Well, I've yet to find ANY utility that uses it.  I hope this
gets better in 4.2, since even ScrFT is broken in 4.1.  Oh, that reminds
me: DEBUG does appear to use ScrFT, although it suffers the same
problems that all the other utilities seem to be having with it (access
violations, mostly).