Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/3/84; site panda.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!whuxlm!harpo!decvax!genrad!panda!mlf
From: mlf@panda.UUCP (Matt L. Fichtenbaum)
Newsgroups: net.decus
Subject: TECO under VMS 4.1
Message-ID: <423@panda.UUCP>
Date: Tue, 2-Apr-85 16:33:40 EST
Article-I.D.: panda.423
Posted: Tue Apr  2 16:33:40 1985
Date-Received: Thu, 4-Apr-85 05:51:17 EST
Distribution: net
Organization: GenRad, Inc., Concord, Mass.
Lines: 33

.....

   OK, here's a problem for which I seek help.

   We have a VAX (750) running VMS.  We used to have lots of
VAXes running VMS, but switched some over to Un*x, but that's
another story.  We also have a TECO (fancy, cryptic editor)
that was apparently obtained from DECUS and is unsupported
by everybody.

   We just upgraded (?) this VAX to VMS 4.1.  Now, TECO has
a mode whereby it displays, and maintains, a window showing
the text buffer around the current pointer.  This window
requires a VT-100.

   When we switched to VMS 4.1, the window stopped working.
TECO accepts the command (5,7:w) to enable the window, but
returns 0 as the parameter's value (7:w=), indicating that
it refused to enable the window.

   Anybody have any ideas?  Maybe the new terminal driver
does something differently, and TECO hasn't learned there's
really a usable terminal out there.  I would be grateful for
any suggestions.

   I'll be more likely to notice suggestions sent by mail.
Thanks!

-- 

					Matt Fichtenbaum
					"Our job is to rescue fires,
					not put out your cat."