markh@squirrel.LABS.TEK.COM (Mark C. Henderson) (12/06/90)
Archive-name: editors/teco/usc.edu/1990-12-06 Archive-directory: usc.edu:/pub/teco/ [128.125.1.45] Original-posting-by: markh@squirrel.LABS.TEK.COM (Mark C. Henderson) Original-subject: Re: TECO (was: MULTICS and the Jargon File) Reposted-by: emv@ox.com (Edward Vielmetti) In article <1990Dec04.235552.4027@dirtydog.ima.isc.com> karl@ima.isc.com (Karl Heuer) writes: >... >Anybody happen to know where the source to Unix teco might be archived? >I used to have a copy, but the source got deleted a few years ago. > >(You can praise modern screen editors all you want, but I've never seen any >tool that can beat TECO for tasks like "add one to each integer in the >buffer".) > >Karl W. Z. Heuer (karl@ima.isc.com or uunet!ima!karl), The Walking Lint You can find all sorts of TECO goodies available by anonymous ftp from usc.edu in ~ftp/pub/teco. This TECO archive is maintained by Pete Siemsen, siemsen%sol.usc.edu@usc.edu. The usc.edu archive includes two versions for Unix. One was originally written for Ultrix by Matt Fichtenbaum and features a VT100 scope mode (also runs under Sun OS). A version of the Ultrix Teco was posted to comp.sources.unix (volume 9). The other version (TECOC) runs nicely on MSDOS and VMS and with a little hacking also works well under SUN OS. The work on the Sun OS port is almost completed. This version has a couple of advantages over the Ultrix version, namely that data structures for the editing buffer are generally more efficient and that the code was written with portability to other operating systems in mind. Mark Henderson -- Mark C. Henderson, Computer Research Laboratory, Tektronix, Inc. MS 50-662, P.O. Box 500, Beaverton, OR 97077, U.S.A. INTERNET: markh@crl.labs.tek.com Tel: +1 503 627 6280 Fax: +1 503 627 5502 MCI MAIL: 378-4996 AT&T Mail: !mchenderson Telex: 6503784996MCI UW
karl_kleinpaste@cis.ohio-state.edu (12/06/90)
Archive-name: editors/teco/teco/1990-12-05
Archive-directory: gatekeeper.dec.com:/pub/comp.sources.unix/volume9/teco/ [16.1.0.2]
Original-posting-by: karl_kleinpaste@cis.ohio-state.edu
Original-subject: Re: TECO (was: MULTICS and the Jargon File)
Reposted-by: emv@ox.com (Edward Vielmetti)
karl@ima.isc.com writes:
Anybody happen to know where the source to Unix teco might be archived?
Pick your transport...
ftp: cheops.cis.ohio-state.edu:pub/
comp.sources.unix/Volume09/teco.[1-4].Z.
uucp: osu-cis!~/siemsen@sol.usc.edu (Pete Siemsen) (12/20/90)
Archive-name: editors/teco/teco/1990-12-19 Archive-directory: usc.edu:/pub/teco/ [128.125.1.45] Original-posting-by: siemsen@sol.usc.edu (Pete Siemsen) Original-subject: Re: TECO (was Re: the jargon file) Reposted-by: emv@ox.com (Edward Vielmetti) rice@dg-rtp.dg.com (Brian Rice) writes: >In article <ZIPPY.90Dec18012554@chaos.cs.brandeis.edu>, >zippy@chaos.cs.brandeis.edu (Patrick Tufts) writes: >|> Where *is* TECO alive? You can ftp TECO stuff from usc.edu in directory /pub/teco. This directory contains the DECUS TECO Collection, which I maintain. It has several TECOs for various platforms, many TECO macros, the latest Standard TECO Manual (DEC's manual, but a newer version than they distribute) and other things relating to TECO. TECO is available in various forms for VAX/VMS, RSX, RT-11, RSTS, Tops, Tenex, Unix, MS-DOS, the Macintosh OS, and (soon) the Amiga. >Not too long ago, I worked >at a VMS site...there was a certain file-manipulation task, I >don't remember precisely what, which was most easily accomplished >by EDIT/TECO'ing the file and immediately saving it (with >EX<esc><esc>). Maybe it was removing trailing spaces from >each line or some such. But I found TECO invaluable for it. It was probably to deal with the output of DEC's RUNOFF utility, which produces files with "record attributes" set to nothing. This allows RUNOFF to do overstriking and underlining of characters on standard line printers by overprinting lines. It's a pain if you want to read the file with most programs, because they are used to "normal" files, which have "implied carriage return" record attributes. So if you use a text editor to look at a file that was produced by RUNOFF, you may get the line-feeds that are in the file plus the line-feeds injected by your editor. DEC's documented method for "normalizing" these files was to run TECO on the file and exit immediately. >I seem to remember this trick being documented, rather out >of the blue, in that little "Using the VMS Editors" book. See the appendices of older RUNOFF (also called DSR) manuals. I think manuals through version 4 of VMS still mentioned TECO. Newer manuals don't. -- Pete Siemsen Pete Siemsen siemsen@usc.edu University of Southern California 645 Ohio Ave. #302 (213) 740-7391 (w) 1020 West Jefferson Blvd. Long Beach, CA 90814 (213) 433-3059 (h) Los Angeles, CA 90089-0251