Path: utzoo!mnetor!uunet!husc6!bbn!uwmcsd1!ig!agate!ucbvax!ucdavis!iris!hildum
From: hildum@iris.ucdavis.edu (Eric Hildum)
Newsgroups: comp.os.vms
Subject: Re: Using an ANSI emulator with VMS editors
Message-ID: <1112@ucdavis.ucdavis.edu>
Date: 12 Feb 88 06:01:15 GMT
References: <2058@bsu-cs.UUCP> <719@ddsw1.UUCP>
Sender: uucp@ucdavis.ucdavis.edu
Reply-To: hildum@iris.UUCP (Eric Hildum)
Organization: U.C. Davis - College of Engineering
Lines: 34

In article <719@ddsw1.UUCP> karl@ddsw1.UUCP (Karl Denninger) writes:
>The biggest problem with VAX/VMS and terminals (in my opinion) is that you 
>can't make your own termcap entries.  The software knows of only a few 
>terminals -- all DEC products.  (Ever wonder why there's such a market for
>VT100/VT220 look-alike terminals?  Now you know!)
>

The VAX/VMS Run-Time Library Routines Reference Manual describes in
great detail how to support other manufacturers terminals.  Check
section 3.10 (pages 3-27 through 3-49) for the proper method of
support.

For those people interested  in developing code using the screen
management routines, the bulk of chapter three is devoted to
explaining the routines and how to PROPERLY use them.

Too often I have seen stupidly written code for VMS.  Now I understand
why, the engineers for these companies are spending too much time
complaining about why VMS doesn't do what they want, and not enough
time learning that, in fact, the solution is already there.

>Your only solution would be to write a filter routine which you insert in
>your terminal program (or pipe to/from it) that translates *all* the DEC
>control codes to what uport wants to see.  Yuck.
>
>-------
>Karl Denninger		       |  Data: +1 312 566-8912
>Macro Computer Solutions, Inc. | Voice: +1 312 566-8910
>...ihnp4!ddsw1!karl	       | "Quality solutions for work or play"


				dehildum@ucdavis.ucdavis.edu	(Internet)
				dehildum@ucdavis.bitnet	(BITNET)
				ucbvax!ucdavis!dehildum	(uucp)