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 vu-vlsi.UUCP Path: utzoo!watmath!clyde!cbosgd!ukma!psuvm.bitnet!psuvax1!vu-vlsi!perry From: perry@vu-vlsi.UUCP (Rick Perry) Newsgroups: net.sources.bugs Subject: Re: Unix Pascal VT100 Graphic Procedures Message-ID: <231@vu-vlsi.UUCP> Date: Thu, 6-Feb-86 19:02:07 EST Article-I.D.: vu-vlsi.231 Posted: Thu Feb 6 19:02:07 1986 Date-Received: Sun, 9-Feb-86 07:29:49 EST References: <360@ihnet.UUCP> Distribution: net Organization: Villanova Univ. EE Dept. Lines: 30 Summary: use chr(27) not literal ESC! > Following are some Procedures to fully use the vt100 terminal > it is uuencoded because of non printing characters. > ... There are a lot of reasons for preferring chr(27) over '' and even chr(9) instead of "", chr(7) instead of literal bells... Some compilers won't even accept "non-printable" chars in literal strings; what does YOUR printer do when it gets a literal ESC[0j ??? using 'more' to read the uudecoded version of your file did wierd things to my vt100! and then there's the whole necessity for uuencode/decode in the first place. ----- write( chr(27), 'rest of cmd' ) { would be ok... } ----- CONST ESC=27; ... write( chr(ESC), 'etc' ) { would be even better... } ----- CONST ESC=chr(27); ... write( ESC, 'etc' ) { would be great if all compilers would take it! } ----- Anyway, thanks for the sources, they look very useful, and certainly handier than trying to uudecode the DEC-vt100 manuals... ...Rick Perry ...{pyrnj,psuvax1}!vu-vlsi!perry