Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!ames!pacbell!att!homxb!homxc!marty
From: marty@homxc.UUCP (M.B.BRILLIANT)
Newsgroups: comp.sys.ibm.pc
Subject: Re: VT100 Emulation
Message-ID: <5895@homxc.UUCP>
Date: 10 Mar 89 16:31:49 GMT
References: <3228@ihuxv.ATT.COM>
Organization: AT&T Bell Laboratories, Holmdel
Lines: 27

From article <3228@ihuxv.ATT.COM>, by mcgregor@ihuxv.ATT.COM (MacGregor):
> Has anyone had success in getting Lotus Corporation's "Symphony" program
> to talk to UNIX(tm) environment.  The Symphony program supplies a VT100.app
> .....
> Unfortunately, the emulation is not robust.  The emulator does not
> accurrately track crusor movements generated by VI.

It isn't just Symphony.  I've used (or tried out) VT100 or VT102
emulations in Procomm, ProComm-Plus-TD, Qmodem, Boyan, Telix, and an
old Ptel.  None of them provide a termcap or terminfo entry for the
emulation.  Only Ptel (kudos! kudos!) lists the escape sequences that
the terminal emulation is designed to respond to.  I used the Ptel
specification to write a terminfo entry, and though it had bugs, it was
a good start.  (My Ptel is for sale: $5).

Now that UNIX(R) is becoming a standard (maybe even two standards :-),
I hope we will soon get termcap and terminfo entries from the vendors
of terminal emulators.  At the very least, the vendor of a terminal
emulator should (as Phoenix did for Ptel) document its interface
specifications.

M. B. Brilliant					Marty
AT&T-BL HO 3D-520	(201) 949-1858		Home (201) 946-8147
Holmdel, NJ 07733	att!homxc!marty

Disclaimer: Opinions stated herein are mine unless and until my employer
	    explicitly claims them; then I lose all rights to them.