Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rutgers!sri-spam!mordor!lll-tis!ptsfa!dual!ucbvax!ubvms.BITNET!ACSCCRA From: ACSCCRA@ubvms.BITNET ("Curtis R. Anderson") Newsgroups: comp.os.vms Subject: Re: SET TERM/MESS_UP_SETTINGS Message-ID: <8706210321.AA18123@ucbvax.Berkeley.EDU> Date: Tue, 16-Jun-87 12:12:00 EDT Article-I.D.: ucbvax.8706210321.AA18123 Posted: Tue Jun 16 12:12:00 1987 Date-Received: Mon, 22-Jun-87 06:42:16 EDT Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 31 >It has always done this, atleast since 4.0. It annoyed me enough, since >I typically needed backspace and the escape character to add a line to >my login.com file which sets the terminal back once SET TERM/INQUIRE >changes it. I got it from the VT240 programmer's manual. It is > [61"p The inherent problem with using SET TERM/INQUIRE occurs with VT-100 COMPATIBLE terminals that may not respond correctly when inquired (an Z sent to a Wyse 85 terminal (VT-220 compatible) in VT-100 mode will issue 85 ). I end up having a LOGIN.TXT file TYPEd by my LOGIN.COM to issue the VT-200 7 bit mode to my Wyse 85 at home and any VT-220 that I use at the university, simply: [62;1p This is all fine and dandy if you always sit at a VT-220 compatible, but if one doesn't mind a 'p' being displayed by the sequence on VT-100 compatibles (and some of them are rather inconsistent, anyway). Exactly how well is ANSI being followed? I take Digital for adherence to standards, and Wyse for value... +------------------------------------------+-----------------------------------+ | Curtis R. Anderson | | | UCS Student Consultant | Syntax: | | | | | ACSCCRA@UBVMS.BITNET | A levy placed on wrongdoing. | | SnailNet: | | | State University of New York at Buffalo | | | 220 Computing Center | | | Buffalo, NY 14260 USA | | +------------------------------------------+-----------------------------------+