Standard TECO TEXT EDITOR AND CORRECTOR FOR THE PDP-11, PDP-10, and PDP-8 USER'S GUIDE AND LANGUAGE REFERENCE MANUAL Special Fall '79 DECUS Edition - December 1979 Modified - November 1980 TECO-11 VERSION 35 TECO-10 VERSION 1 TECO-8 VERSION 7 November, 1980 Standard TECO Page ii The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation or by DECUS. Neither Digital Equipment Corporation, DECUS, nor the authors assume any responsibility for the use or reliability of this document or the described software. Copyright (C) 1979 TECO SIG General permission to copy or modify, but not for profit, is hereby granted, provided that the above copyright notice is included and reference made to the fact that reproduction privileges were granted by the TECO SIG. Standard TECO Page iii CONTENTS INTRODUCTION vi CHAPTER 1 BASICS OF TECO 1-1 1.1 USING TECO 1-1 1.2 DATA STRUCTURE FUNDAMENTALS 1-3 1.3 FILE SELECTION COMMANDS 1-4 1.3.1 Simplified File Selection 1-4 1.3.2 Input File Specification (ER command) 1-5 1.3.3 Output File Specification (EW command) 1-6 1.3.4 Closing Files (EX command) 1-7 1.4 INPUT AND OUTPUT COMMANDS 1-8 1.5 POINTER POSITIONING COMMANDS 1-9 1.6 TYPE OUT COMMANDS 1-10 1.6.1 Immediate Action Commands 1-11 1.7 TEXT MODIFICATION COMMANDS 1-12 1.8 SEARCH COMMANDS 1-13 1.9 SAMPLE EDITING JOB 1-14 INTERLUDE 1-17 CHAPTER 2 INVOKING TECO 2-1 2.1 RUNNING TECO 2-1 2.2 CREATING A NEW FILE 2-1 2.3 EDITING AN EXISTING FILE 2-1 2.4 SWITCHES ON TECO AND MAKE COMMANDS 2-2 2.5 INVOKING A TECO PROGRAM 2-3 2.6 USER INITIALIZATION 2-3 CHAPTER 3 CONVENTIONS AND STRUCTURES 3-1 3.0 TECO CHARACTER SET 3-1 3.1 TECO COMMAND FORMAT 3-1 3.1.1 Numeric Arguments 3-2 3.1.2 Text Arguments 3-4 3.1.3 Colon Modifiers 3-5 3.2 DATA STRUCTURES 3-6 3.2.1 Text Buffer 3-7 3.2.2 Q-registers 3-8 3.2.3 Q-register Push-down List 3-9 3.2.4 Numeric Values and Flags 3-9 3.3 SCOPE SUPPORT 3-10 CHAPTER 4 COMMAND STRING EDITING 4-1 Standard TECO Page iv CHAPTER 5 LOGICAL COMMAND SUMMARY 5-1 5.1 FILE SPECIFICATION COMMANDS 5-2 5.2 PAGE MANIPULATION COMMANDS 5-11 5.3 BUFFER POINTER MANIPULATION COMMANDS 5-13 5.4 TEXT TYPE OUT COMMANDS 5-15 5.5 DELETION COMMANDS 5-18 5.6 INSERTION COMMANDS 5-20 5.7 SEARCH COMMANDS 5-22 5.8 SEARCH ARGUMENTS 5-27 5.9 Q-REGISTERS 5-31 5.10 ARITHMETIC AND EXPRESSIONS 5-35 5.11 SPECIAL NUMERIC VALUES 5-38 5.12 COMMAND LOOPS 5-42 5.13 BRANCHING COMMANDS 5-43 5.14 CONDITIONAL EXECUTION COMMANDS 5-48 5.15 RETRIEVING ENVIRONMENT CHARACTERISTICS 5-50 5.16 MODE CONTROL FLAGS 5-52 5.17 SCOPE COMMANDS 5-58 5.18 PROGRAMMING AIDS 5-62 5.18.1 Text Formatting 5-62 5.18.2 Comments 5-62 5.18.3 Messages 5-63 5.18.4 Tracing 5-64 5.18.5 Convenience Characters 5-65 5.18.6 Memory Expansion 5-65 5.18.7 Case Control 5-66 5.19 MANIPULATING LARGE PAGES 5-67 5.20 TECHNIQUES AND EXAMPLES 5-68 CHAPTER 6 ALPHABETICAL COMMAND SUMMARY 6-1 CHAPTER 7 ERROR MESSAGE PROCESSING 7-1 7.1 ERROR MESSAGES 7-1 7.2 IMPLEMENTATION-SPECIFIC ERROR MESSAGES 7-2 7.2.1 TECO-11 Error Messages 7-2 7.2.2 TECO-10 Error Messages 7-4 7.2.3 TECO-8 Error Messages 7-21 Standard TECO Page v APPENDIX A ASCII CHARACTER SET A-1 APPENDIX B ERROR MESSAGE SUMMARY B-1 APPENDIX C INCOMPATIBLE, OBSOLETE, AND SYSTEM-SPECIFIC COMMANDS C-1 C.1 SPECIFIC FEATURES OF TECO-11 C-1 C.1.1 TECO Commands C-1 C.1.2 String Build Constructs C-3 C.2 SPECIFIC FEATURES OF OS/8 C-3 C.3 SPECIFIC FEATURES OF RSX-11/M, RSX-11/D, IAS, and VAX/VMS C-3 C.4 SPECIFIC FEATURES OF RSTS/E C-4 C.5 SPECIFIC FEATURES OF TOPS-10 C-6 APPENDIX D RT-11 OPERATING CHARACTERISTICS D-1 APPENDIX E RSTS/E OPERATING CHARACTERISTICS E-1 APPENDIX F RSX-11 OPERATING CHARACTERISTICS F-1 APPENDIX G VAX/VMS OPERATING CHARACTERISTICS G-1 APPENDIX H OS/8 OPERATING CHARACTERISTICS H-1 APPENDIX I TOPS-10 OPERATING CHARACTERISTICS I-1 APPENDIX J TECO.TEC & TECO.INI J-1 APPENDIX K CONFIGURING RSTS/E TECO-11 K-1 APPENDIX L CONFIGURING TECO-11 FOR FOREIGN SCOPES L-1 APPENDIX M STORAGE AREAS M-1 APPENDIX N GLOSSARY N-1 Standard TECO Page vi Introduction INTRODUCTION TECO is a powerful text editing program that runs under most DIGITAL operating systems. TECO may be used to edit any form of ASCII text: program sources, manuscripts, or correspondence, for example. Since TECO is a character-oriented editor rather than a line editor, text edited with TECO does not have line numbers associated with it, and it is not necessary to replace an entire line of text in order to change one character. The versatility of TECO makes it complex. To help users deal with this complexity, this manual presents TECO in two stages. The first part (Chapter 1) contains basic information and introduces enough TECO commands to allow the novice TECO user to begin creating and editing text files after only a few hours of instruction. The introductory commands are sufficient for any editing application; however, they are less powerful, in many cases, than the advanced commands presented later. Subsequent chapters describe the full TECO command set, including a review of the introductory commands presented in Chapter 1. These chapters also introduce the concept of TECO as a programming language and explain how basic editing commands may be combined into "programs" sophisticated enough to handle the most complicated editing tasks. The early sections of this manual include few specific examples of commands, since all TECO commands have a consistent, logical format which will quickly become apparent to the novice user. However, the end of Chapter 1 does include an extensive example employing most of the commands introduced up to that point. Students of TECO should experiment with each command as it is introduced, then duplicate the examples on their computer. This manual is intended to be a reference manual and, except for Chapter 1, is not a tutorial. After Chapter 1, it is assumed that the reader has a general familiarity with TECO and is referring to this manual to find detailed information. Standard TECO Page vii Introduction The following notation is used in this manual to represent special characters: Notation ASCII code (octal) Name 0 Null 10 Backspace 11 Tab 12 Line Feed 13 Vertical Tab 14 Form Feed 15 Carriage Return or $ 33 Escape or Alt Mode - Control-x 40 Space 177 Delete or Rubout Control characters are produced by striking the CONTROL key and a character key simultaneously. Throughout this manual, upper case characters will be used to represent TECO commands. Standard TECO Page viii Introduction Standard TECO Page 1-1 Basics of TECO CHAPTER 1 BASICS OF TECO 1.1 USING TECO TECO may be called from command level by typing the appropriate command, followed by a carriage return: For RT-11, OS/8, and TOPS-10 R TECO For RSTS/E RUN $TECO For RSX-11 RUN $TEC For VAX/VMS RUN SYS$SYSTEM:TEC TECO will respond by printing an asterisk at the left margin to indicate that it is ready to accept user commands. At this point, you may type one or more commands. A TECO command consists of one or two characters which cause a specific operation to be performed. Some TECO commands may be preceded or followed by arguments. Arguments may be either numeric or textual. A numeric argument is simply an integer value which can be used to indicate such items as the number of times a command should be executed. A text argument is a string of ASCII characters which might be words of text, for example, or a file specification. If a command requires a numeric argument, the numeric argument always precedes the command. If a command requires a text argument, the text argument always follows the command. All text arguments are terminated by a special character (usually an ESCAPE) which indicates to TECO that the next character typed will be the first character of a new command. TECO will execute commands upon receipt of two consecutive ESCAPE characters. The ESCAPE is a non-printing character which may be labelled ESC, ALT, or PREFIX on your keyboard. TECO echoes a dollar sign ($) whenever an ESCAPE is typed. The dollar sign character is used in examples throughout this manual to represent ESCAPE. Note that the carriage return character has no special significance to TECO. Only the double ESCAPE forces execution of the command string. TECO executes command strings from left to right until either all commands have been executed or a command error is recognized. It then prints an asterisk to signal that additional commands may be entered. Standard TECO Page 1-2 Using TECO If TECO encounters an erroneous command, it prints an error message and ignores the erroneous command as well as all commands which follow it. All error messages are of the form: ?XXX Message where XXX is an error code and the message is a description of the error. Some error messages mention the specific character or string of characters in error. In these error messages, TECO represents the non-printing special characters as follows: Character Form Displayed Every error message is followed by an asterisk at the left margin, indicating that TECO is ready to accept additional commands. If you type a single question mark character (?) after a TECO-generated error message, TECO will print the erroneous command string up to and including the character which caused the error message. This helps you to find errors in long command strings and to determine how much of a command string was executed before the error was encountered. You can correct errors in commands (as in other text typed) by hitting the DELETE key, which may be labeled DEL or RUBOUT on your keyboard. Each depression of the DELETE key deletes one character and echoes it on your terminal, beginning with the last character typed. If your terminal is a CRT, TECO may actually erase the deleted character from the screen. You can delete an entire command string this way, if necessary. To delete an entire line of commands, enter the character , typed by holding down the CONTROL key while depressing the "U" key. When you are done editing, use the EX command to exit TECO, as described below in section 1.3.4. Standard TECO Page 1-3 Data Structure Fundamentals 1.2 DATA STRUCTURE FUNDAMENTALS TECO considers any string of ASCII codes to be text. Text is broken down into units of characters, lines, and pages. A character is one ASCII code. A line of text is a string of ASCII codes including one line terminator (usually a line feed) as the last character on the line. A page of text is a string of ASCII codes including one form feed character as the last character on the page. TECO maintains a text buffer in which text is stored. The buffer usually contains one page of text, but the terminating form feed character never appears in the buffer. TECO also maintains a buffer pointer. The pointer is a movable position indicator which is never located directly on a character, but is always between characters: between two characters in the buffer, before the first character in the buffer, or after the last character in the buffer. Line feed and form feed characters are inserted automatically by TECO. A line feed is automatically appended to every carriage return typed to TECO and a form feed is appended to the contents of the buffer by certain output commands. Additional line feed and form feed characters may be entered into the buffer as text. If a form feed character is entered into the buffer, it will cause a page break upon output; text following the form feed will begin a new page. Finally, TECO maintains an input file and an output file, both of which are selected by the user through file specification commands. The input file may be on any device from which text may be accepted. The output file may be on any device on which edited text may be written. TECO functions as a "pipeline" editor. Text is read from the input file into the text buffer, and is written from the buffer onto the output file. Once text has been written to the output file, it cannot be accessed again without closing the output file and reopening it as an input file. Standard TECO Page 1-4 File Selection Commands 1.3 FILE SELECTION COMMANDS Input and output files may be specified to TECO in several ways. The following sections present first a simple method for specifying files, and then more sophisticated commands that permit flexible file selection. NOTE All of the following file selection commands are shown with a general argument of "filespec". The actual contents of this filespec argument are operating system dependent. See the operating characteristics appendices. Examples include a mixture of file specifications from various operating systems. 1.3.1 Simplified File Selection For most simple applications, you can use special operating system commands to specify the name of the file you wish to edit at the same time that you start up TECO. TO CREATE A NEW FILE For RSTS/E, RSX-11, VAX/VMS, OS/8, TOPS-10 MAKE filespec For RT-11 EDIT/CREATE filespec These commands start up TECO and perform an effective EWfilespec$ command (see Section 1.3.3). EDITING AN EXISTING FILE For RSTS/E, RSX-11, VAX/VMS, OS-8, TOPS-10 TECO filespec For RT-11 EDIT filespec These commands start up TECO and open the specified file for editing while preserving the original file (as a backup file). They also automatically bring the first page of the file into the text buffer. These functions simulate the EB command described in Chapter 5. If any of the above commands do not seem to work on your operating system, consult the appropriate appendix for information about how to install TECO and its associated operating system commands. Standard TECO Page 1-5 File Selection Commands 1.3.2 Input File Specification (ER command) TECO will accept input text from any input device in the operating system. The input device may be specified by means of an ER command terminated by an ESCAPE. The ER command causes TECO to open the specified file and print an error message if the file is not found. This command does not cause any portion of the file to be read into the text buffer, however. The following examples illustrate use of the ER command. COMMAND FUNCTION ERfilespec$ General form of the ER command where "filespec" is the designation of the input file. The command is terminated by an ESCAPE, which echoes as a dollar sign. ERPR:$ Prepare to read an input file from the paper tape reader. ERPROG.MAC$ Prepare to read input file PROG.MAC from the system's default device. ERDX1:PROG.FOR$ Prepare to read input file PROG.FOR from DX1:. TECO will only keep one input and one output file open and selected at a time. The current input file may be changed by simply using the ER command to specify a new file. Remember that it is not always necessary to specify an input file. If you want to create a file without using any previously edited text as input, you may type commands to insert the necessary text directly into the text buffer from the keyboard and, at the end of each page, write the contents of the buffer onto an output file. Since all input is supplied from the keyboard, no input file is necessary. Standard TECO Page 1-6 File Selection Commands 1.3.3 Output File Specification (EW command) TECO will write output text onto any device in the operating system. The output file may be specified by means of an EW command terminated by an ESCAPE. If the output device is a file-structured device (for example, a disk), the file name and any extension must be supplied. If a file name is specified but no device is explicitly defined, the system's default device is assumed. The following examples illustrate use of the EW command. COMMAND FUNCTION EWfilespec$ General form of the EW command where "filespec" is the designation of the output file. The command is terminated by an ESCAPE, which echoes as a dollar sign. EWSYS:TEXT.LST$ Prepare to write output file TEXT.LST on SYS:. EWPROG$ Prepare to write output file PROG on the system's default device. ERDX1:INPUT.MAC$EWOUTPUT.MAC$$ Open an input file INPUT.MAC to be found on DX1: and open an output file named OUTPUT.MAC. The double ESCAPE ($$) terminates the command string and causes the string to be executed. Note that the ESCAPE which terminates the EW command may be one of the two ESCAPEs which terminates the command string. You do not need to specify an output file if you only want to examine an input file, without making permanent changes or corrections. In this case, the contents of the input file may be read into the text buffer page by page and examined at the terminal. Since all output is printed on the user terminal, no output file is needed. Standard TECO Page 1-7 File Selection Commands 1.3.4 Closing Files (EX command) When you are finished editing a file, use the EX command to close out the file and exit from TECO. The current contents of the text buffer and any portion of the input file that has not been read yet are copied to the output file before TECO exits. The EX command takes no arguments. COMMAND: EX FUNCTION: Write the text buffer to the current output file, move the remainder of the current input file to the current output file, close the output file, then return to the operating system. COMMAND STRING: ERFILE.MAC$EWCOPY.MAC$EX$$ FUNCTION: Open an input file FILE.MAC and open an output file named COPY.MAC, then copy all the text in the input file to the output file, close the output file, and exit from TECO. Standard TECO Page 1-8 Input and Output Commands 1.4 INPUT AND OUTPUT COMMANDS The following commands permit pages of text to be read into the TECO text buffer from an input device or written from the buffer onto an output device. Once a page of text has been written onto the output file, it cannot be recalled into the text buffer unless the output file is closed and reopened as an input file. COMMAND FUNCTION Y Clear the text buffer, then read the next page of the input file into the buffer. Since the Y command causes the contents of the text buffer to be lost, it is not permitted if an output file is open and there is text in the buffer. P Write the contents of the text buffer onto the next page of the output file, then clear the buffer and read the next page of the input file into the buffer. nP Execute the P command n times, where n must be a positive (non-zero) integer. If n is not specified, a value of 1 is assumed. After each Y, P, or nP command, TECO positions the pointer before the first character in the buffer. Standard TECO Page 1-9 Pointer Positioning Commands 1.5 POINTER POSITIONING COMMANDS The buffer pointer provides the only means of specifying the location within a block of text at which insertions, deletions or corrections are to be made. The following commands permit the buffer pointer to be moved to a position between any two adjacent characters in the buffer. COMMAND FUNCTION J Move the pointer to the beginning of the buffer. L Move the pointer forward to a position between the next line feed and the first character of the next line. That is, advance the pointer to the beginning of the next line. nL Execute the L command n times, where n is a signed integer. A positive value of n moves the pointer to the beginning of the nth line following the current pointer position. A negative value moves the pointer backward n lines and positions it at the beginnning of the nth line preceding the current position. If n is zero, the pointer is moved to the beginning of the line on which it is currently positioned. C Advance the pointer forward across one character. nC Execute the C command n times, where n is a signed integer. A positive value of n moves the pointer forward across n characters. A negative value of n moves the pointer backward across n characters. If n is zero, the pointer position is not changed. Remember that there are two characters, and , at the end of each line in the buffer. These commands may be used to move the buffer pointer across any number of lines or characters in either direction; however, they will not move the pointer across a page boundary. If a C command attempts to move the pointer backward beyond the beginning of the buffer or forward past the end of the buffer, an error message is printed and the command is ignored. If an L command attempts to exceed the page boundaries in this manner, the pointer is positioned at the boundary which would have been exceeded. Thus, in a page of 2000 lines, the command "-4000L" would position the pointer before the first character in the buffer. The command "4000L" would position the pointer after the last character in the buffer. No error message is printed in either case. Standard TECO Page 1-10 Type Out Commands 1.6 TYPE OUT COMMANDS The following commands permit sections of the text in the buffer to be printed out on your terminal for examination. These commands do not move the buffer pointer. COMMAND FUNCTION T Type the contents of the text buffer from the current position of the pointer through and including the next line feed character. nT Type n lines, where n is a signed integer. A positive value of n causes the n lines following the pointer to be typed. A negative value of n causes the n lines preceding the pointer to be typed. If n is zero, the contents of the buffer from the beginning of the line on which the pointer is located up to the pointer is typed. This is useful for locating the buffer pointer, or for verifying its location. HT Type the entire contents of the text buffer. V Type the current line. Equivalent to the sequence "0TT". Standard TECO Page 1-11 Type Out Commands 1.6.1 Immediate Action Commands In addition, there are two special type out commands available as a convenience. They are abbreviations for two frequently used commands. These commands consist of a single character and must be the very first character typed after TECO prints its prompting asterisk. They take effect immediately; there is no need to follow these commands by an ESCAPE character. For this reason, these commands are known as immediate action commands. COMMAND FUNCTION Immediately execute the LT command. This command is issued by typing the line feed key as the first keystroke after TECO's prompt. It causes TECO to move ahead one line and then type out the new line. Immediately execute the -LT command. This command is issued by typing the backspace key as the first keystroke after TECO's prompt. It causes TECO to move back one line and then type the line just moved over on the terminal. On terminals with no backspace key, typing has the same effect. These commands are useful for "walking through" a file, examining and/or modifying lines one at a time. Note that on TECO-11, does nothing if you are at the top of the buffer, and does nothing if you are at the bottom of the buffer. Standard TECO Page 1-12 Text Modification Commands 1.7 TEXT MODIFICATION COMMANDS You can insert or delete text from the buffer using the following commands: COMMAND FUNCTION Itext$ Where "text" is a string of ASCII characters terminated by an ESCAPE (which echoes as a dollar sign), the specified text is inserted into the buffer at the current position of the pointer. The pointer is repositioned immediately after the last character of the insertion. K Delete the contents of the text buffer from the current position of the pointer up to and including the next line feed character. nK Execute the K command n times, where n is a signed integer. A positive value of n causes the n lines following the pointer to be deleted. A negative value of n causes the n lines preceding the pointer to be deleted. If n is zero, the contents of the buffer from the beginning of the line on which the pointer is located up to the pointer is deleted. HK Delete the entire contents of the text buffer. D Delete the character following the buffer pointer. nD Execute the D command n times, where n is a signed integer. A positive value of n causes the n characters following the pointer to be deleted. A negative value of n causes the n characters preceding the pointer to be deleted. If n is zero, the command is ignored. Like the L and C commands, the K and D commands may not execute across page boundaries. If a K command attempts to delete text up to and across the beginning or end of the buffer, text will be deleted only up to the buffer boundary and the pointer will be positioned at the boundary. No error message is printed. A D command attempting to delete text past the end or beginning of the text buffer will produce an error message and the command will be ignored. Standard TECO Page 1-13 Search Commands 1.8 SEARCH COMMANDS The following commands may be used to search the input file for a specified string of characters. COMMAND FUNCTION Stext$ Where "text" is a string of ASCII characters terminated with an ESCAPE (which echoes as a dollar sign), this command searches the text buffer for the next occurrence of the specified character string following the current pointer position. If the string is found, the pointer is positioned after the last character on the string. If it is not found, the pointer is positioned immediately before the first character in the buffer and an error message is printed. Ntext$ Performs the same function as the S command except that the search is continued across page boundaries, if necessary, until the character string is found or the end of the input file is reached. If the end of the input file is reached, an error message is printed. You must then close the output file and reopen it as an input file before you can edit the file further. Both the S command and the N command begin searching for the specified character string at the current position of the pointer. Therefore, neither command will locate any occurrence of the character string which precedes the current pointer position, nor will it locate any character string which continues across a page boundary. Both commands execute the search by attempting to match the command argument, character for character, with some portion of the buffer contents. If an N command reaches the end of the buffer without finding a match for its argument, it writes the contents of the buffer onto the output file, clears the buffer, reads the next page of the input file into the buffer, and continues the search. Standard TECO Page 1-14 Sample Editing Job 1.9 SAMPLE EDITING JOB The following sample editing job is included to help the new user to achieve a greater understanding of the basic TECO commands. The entire terminal output from the editing run is reproduced intact, with numbers added in the left margin referring to the explanatory paragraphs which follow. 1< *EWDT1:FILE1.TXT$$ 2< *HKIMR. JOHN P. JONES ! COMPUTER ELECTRONICS CORPORATION ! BOSTON, MASAASACHUSETTS ! ! DEAR MR. JONES: ! ! I WAS PLEASED TO RECEIVE YOUR REQUEST FOR INFORMATION ! PERTAINING TO THE NEW TECO TEXT EDITING AND CORRECTING ! PROGRAM. ! ! ENCLOSED IS A COPY OF THE TECO USERS'S GUIDE, WHICH ! SHOULD ANSWER ALL OF YOUR QUESTIONS. ! ! SINCERELY, ! ! ! ! ! $$ 3< *-20LSETTS$I 02150$$ ! *STION$2C13DIREGARDING$$ 4< *SGUIDE$-5DIMANUAL$$ ! *SELY$0T$$ ! SINCERELY*0KIVERY TRULY YOURS$$ ! *HT$$ ! MR. JOHN P. JONES ! COMPUTER ELECTRONICS CORPORATION ! BOSTON, MASSACHUSETTS 02150 ! ! DEAR MR. JONES: ! ! I WAS PLEASED TO RECEIVE YOUR REQUEST FOR INFORMATION ! REGARDING THE NEW TECO TEXT EDITING AND CORRECTING ! PROGRAM. ! ! ENCLOSED IS A COPY OF THE TECO USER'S MANUAL, WHICH ! SHOULD ANSWER ALL OF YOUR QUESTIONS. ! ! VERY TRULY YOURS, ! ! ! Standard TECO Page 1-15 Sample Editing Job ! ! 5< *EX$$ ! (TECO is rerun, operating system dependent) ! *ERDT1:FILE1.TXT$EWLP:$$ 6< *Y5KIMR. JAMES B. SMITH ! DATEK ASSOCIATES, INC. ! 122 MAIN STREET WEST ! AUSTIN, TEXAS ! ! DEAR MR. SMITH: ! $$ ! *HT$$ ! MR. JAMES B. SMITH ! DATEK ASSOCIATES, INC. ! 122 MAIN STREET WEST ! AUSTIN, TEXAS ! ! DEAR MR. SMITH: ! ! I WAS PLEASED TO RECEIVE YOUR REQUEST FOR INFORMATION ! REGARDING THE NEW TECO TEXT EDITING AND CORRECTING ! PROGRAM. ! ! ENCLOSED IS A COPY OF THE TECO USER'S MANUAL, WHICH ! SHOULD ANSWER ALL OF YOUR QUESTIONS. ! ! VERY TRULY YOURS, ! ! ! ! ! ! *EX$$ 1) At this point, the user called TECO into memory. TECO responded by printing an asterisk at the left margin. The user then entered an EW command, opening an output file called "FILE1.TXT" on DT1. There is no input file. Upon receipt of the double ESCAPE ($$), TECO created the designated output file, then printed another asterisk at the left margin. 2) The user entered a command string consisting of two commands. The HK command cleared the text buffer (not really necessary, since it was already empty), and the I command inserted 18 lines of text into the buffer, including 8 blank lines. TECO executed these commands upon receipt of the second double ESCAPE. At this point, the buffer pointer was positioned at the end of the buffer, following the last line feed character in the text. Note that the user made an error while typing the word "MASSACHUSETTS". He typed "MASA", then realized his mistake and struck the DELETE key once to delete the second "A". TECO echoed the deleted character. The user then typed the correct Standard TECO Page 1-16 Sample Editing Job character and continued the insertion. 3) The user typed -20L to move the pointer to the beginning of the buffer and SETTS$ to position the pointer immediately after the character string "ETTS" (which terminates the word "MASSACHUSETTS"). He then used an I command to insert one space and a five-digit zip code. A second S command positioned the pointer after the word "INFORMATION". The 2C command moved the pointer to the beginning of the next line (carriage return and line feed count two characters), and the user deleted the words "PERTAINING TO" and replaced them with the word "REGARDING". 4) The user continued editing by positioning the pointer after the word "GUIDE". He then deleted this word, and replaced it with the word "MANUAL". Finally, he searched for the word "SINCERELY", typed 0T to determine that the pointer was correctly positioned between the Y and the comma which follows it, and typed 0K to delete everything on the line except the comma. He then inserted "VERY TRULY YOURS" in place of the word "SINCERELY". An HT command caused the edited text to be printed at the terminal. 5) The command string EX$$ caused the contents of the buffer to be written onto the output file and closed the output file. The user then reentered TECO and reopened the file "FILE1.TXT" as an input file and specified the line printer as an output file. 6) This command string reads the first (and only) page of "FILE1.TXT" into the buffer, deleted the first 5 lines, replaced them with a different address and salutation, then printed the contents of the buffer on the terminal for verification and finally printed the new version of the letter onto the line printer. Note that the previous version of the letter still resides in file "FILE1.TXT" on DT1. Standard TECO Page 1-17 Interlude INTERLUDE The rest of this manual is a description of TECO in all its glory. TECO is a complex editor and has many features because it has been under development for a long time. (TECO is older than some of the readers of this manual!) Do not try to understand everything the first time through. If you find that what you are reading seems hopelessly obscure, or makes no sense whatsoever, skip to the next section and come back to it some time later. It will be a while before you need all of TECO's features. This manual is meant to be a reference manual and not a tutorial. Readers who are first learning TECO may wish to consult the following document (available from Digital Equipment Corporation) for more basic material: DEC-10-UTECA-A-D INTRODUCTION TO TECO. The commands described in this manual are those implemented in TECO-11 Version 35, TECO-8 Version 7, and TECO-10 Version 1. Some of the more obscure commands may not be present under some operating systems, in which case this is indicated by a note in the form [Not in TECO-x]. This manual also describes some (but not necessarily all) of the obscure commands that belong to one implementation of TECO but not to the other two implementations. Such commands are flagged by a note of the form [TECO-x only]. These commands are not to be considered part of the so-called "Standard TECO" and implementors should contact the TECO SIG before implementing these commands on other operating systems. Consult also the appendices for commands that are very operating system dependent. Standard TECO Page 1-18 Interlude Standard TECO Page 2-1 Invoking TECO CHAPTER 2 INVOKING TECO 2.1 RUNNING TECO To run TECO with no special options or defaults, use the same command on your operating system that you would use to run any other program. The command is operating-system dependent but is usually something like RUN TECO Consult the appendix that describes your operating system's characteristics for details. 2.2 CREATING A NEW FILE As described in Chapter 1, most operating systems use the same command to invoke TECO for the purpose of creating a new file: MAKE filespec The "MAKE filespec" command takes as its single argument the file specification for the file to be created. This file specification must conform to the conventions used by your operating system. If a file by that name already exists, TECO will give you a warning message telling you that you are superseding an existing file. The MAKE command invokes TECO and performs an effective EWfilespec$$ TECO command, as described in Chapter 1. 2.3 EDITING AN EXISTING FILE As Chapter 1 states, most operating systems use the same command to invoke TECO for the purpose of editing an existing file: TECO filespec The "TECO filespec" command takes as its argument the file specification for the file to be edited. The file will be opened for input and output, with back-up protection. That means that the system will save the original version of the source file (in case you 'blow' the edit). If your operating system supports file version numbers, a new version will be created. If your operating system does not support file version numbers, the original file will be preserved in a file with the same name but Standard TECO Page 2-2 Editing an Existing File with a backup extension (.BAK). The TECO command invokes TECO and performs an effective EBfilespec$Y$$ command. Note that the first page of the file has already been brought into memory and that the text buffer pointer is positioned at the start of the file. If, at any time during the edit, you discover that the edit is invalid, type enough s to get you back to the operating system. You will find that your original file has been preserved. 2.4 SWITCHES ON TECO and MAKE COMMANDS The TECO and MAKE commands can take switches (qualifiers) of the form /SWITCH. These switches are described below. SWITCHES ON COMMAND LINES System Switch Meaning OS/8 /INSPECT Do not create an output file /VT Load VTEDIT RSTS/E /SIZE:n start with nK word editing area /SIZE:+n start with extra nK words of editing area RSTS/E RSX-11 VAX/VMS /INSPECT Do not create an output file /FIND Initially position to the position marker left in the file by the VTEDIT macro and delete the marker. /NOCREATE Do not automatically create a new file if the file specified by the TECO command does not exist. /NOINI Do not use TECO.INI to perform initialization /NOMEMORY Do not remember the argument to the invocation command. /SCROLL Automatically enter split screen scrolling mode, using 1/4 of the screen's lines as the scrolling area (available on VT100 terminals only). /VTEDIT Load VTEDIT video terminal editor The /SCROLL command may take a switch value of the following form: /SCROLL:n Enter split screen scrolling mode, using n lines for the scrolling area. Standard TECO Page 2-3 Switches on TECO and MAKE Commands The /VTEDIT command may also take switch values (of the form :value). /VTEDIT:HOLD Start up in hold screen mode /VTEDIT:SEEALL Start up in SEEALL mode These arguments can be combined, viz.: /VTEDIT:HOLD:SEEALL. 2.5 INVOKING A TECO PROGRAM All operating systems except TOPS-10 and RT-11 use the same command to let you start up execution of a TECO program (macro). This is the MUNG command. The MUNG command has the form MUNG filespec where filespec is the name of the TECO program that is to be run. If no file extension (file type) is specified, .TEC is assumed. This command executes the TECO code that appears within the specified file. It invokes TECO and performs an effective EIfilespec$$ command (consult the appendices for operating-system dependent differences). The contents of the specified file should generally end with a double ESCAPE so that execution will start immediately. Another form of this command is MUNG filespec,data where "data" is of any string of ASCII characters to be passed to the TECO program. This version of the MUNG command invokes TECO and issues an effective Idata$EIfilespec$$ command. 2.6 USER INITIALIZATION You can specify initialization commands to TECO by creating a file called TECO.INI. If, upon start-up, TECO finds a file called TECO.INI in your area, TECO executes the commands in that file. You can use TECO.INI commands to set initial values of flags and to tailor TECO to your needs. You must, however, be very careful in constructing code for your TECO.INI file: an error in this code may keep TECO from running at all! If you include unusual commands in your initialization file, you would be prudent to surround such commands with the ? command. This causes TECO to type the commands out when they are executed Standard TECO Page 2-4 User Initialization (see section 5.18.4). You should also print an informative message on the terminal reminding other users that this version of TECO has been customized. Example 1: ?1ED? The user initialization file sets the ED flag to 1 so that ^ characters in search strings have their traditional meaning (do not convert the next character to a control character). The file also causes the command to be typed out when it is executed. Example 2: ED#16ED ^A[Dot preserved on failing searches]^A 13^T 10^T The user initialization file causes future search string failures to preserve the pointer position. It also prints a message informing all users of this feature. In TECO-11, the TECO.INI commands may return a value to the command processor. Such a value, if present, is interpreted as a set of bit encoded flags that control the startup processing. The following bits may be set: Value&1 Automatically load the VTEDIT macro (as if the user had typed TECO/VTEDIT). Value&4 Inhibit use of the memory file (as if the user had typed TECO/NOMEMORY). Value&16 Automatically load VTEDIT and start it in SEEALL mode (as if the user had typed TECO/VTEDIT:SEEALL). Value&32 Automatically load VTEDIT and start it in HOLDSCREEN mode (as if the user had typed TECO/VTEDIT:HOLD). Value&128 Automatically enter split screen scrolling mode (as if the user had typed TECO/SCROLL). Value&256 Inhibit automatic creation of the output file if the input file does not exist (as if the user had typed TECO/NOCREATE). Standard TECO Page 3-1 Conventions and Structures CHAPTER 3 CONVENTIONS AND STRUCTURES 3.0 TECO CHARACTER SET TECO accepts the full 7-bit ASCII character set; all characters have their 8th bit (the parity bit) trimmed off. If your terminal does not transmit or receive all of the ASCII codes, you can still insert the full character set into your TECO buffer, using special commands (see section 5.6). TECO command strings may be entered using upper case characters (as shown throughout this manual) or lower case characters. The commands MQ, mQ, Mq, and mq are treated alike. A file containing upper and lower case text can be edited in the same way as a file containing upper case only, although this may be clumsy to do from an upper case only terminal. TECO can be set to convert lower case alphabetics to upper case as they are typed in; commands to enable or disable lower case type-in will be presented in section 5.16. Control characters are generally echoed by TECO as a caret or up-arrow followed by the character. Some control characters, such as (form feed) and (bell) echo as the function they perform. In many cases, you can type a control character as a caret (up-arrow) followed by a character, and it will be treated as if it had been entered using the control key. There are exceptions to the interchangeable use of the CONTROL key and the caret. When a control character is used as the delimiter of a text string (as explained in Section 3.1.2 below), it must be entered in its form. This form must also be used if the control character is the second character of a two-character command, or is being entered as an immmediate action command. Since certain control characters have special meaning in text arguments, some of them (such as and ), must be entered into a text string using the CONTROL key and preceded by , ^Q, , or ^R. 3.1 TECO COMMAND FORMAT A TECO command consists of one or two characters, optionally preceded by a numeric argument and sometimes followed by a text argument. TECO commands may be strung together by concatenating them into a single command string. No delimiter is necessary between commands, although a single ESCAPE or caret-[ may be inserted between them if desired. This ESCAPE will keep numeric arguments from affecting the commands that follow the ESCAPE. Standard TECO Page 3-2 Conventions and Structures 3.1.1 NUMERIC ARGUMENTS Most TECO commands may be preceded by a numeric argument. Some numeric arguments must be positive; others can be negative or zero. The maximum size of any numeric argument is restricted, as summarized in the following table: signed unsigned system min max max TECO-8 -2**11+1 +2**11-1 2**15-1 TECO-10 -2**34 +2**34-1 2**35-1 TECO-11 -2**15 +2**15-1 2**16-1 TABLE 3-1 Restrictions on numeric arguments Exceeding these ranges of values can cause unpredictable results. So can using a negative argument with a command that takes only an unsigned argument. Numeric arguments can be used in the following ways: - Character commands such as J, C, R, and D take a single numeric argument which represents the number of characters that the command is to act on. - Such commands as P, PW, and < perform an action that can be repeated. The numeric argument is the repetition count. - Some commands, such as ED, ET, E, X, ES, EU, and EV, control the setting of variables called flags. When a numeric argument is specified, the value of that argument becomes the new value of the associated flag. When no numeric argument is specified, these command return the value of the associated flag. - Line commands such as T, K, X, FB, and FC operate on lines. They take zero, one, or two numeric arguments. If one argument (n) is specified, it represents the number of lines over which the command is to have effect, beginning at the current buffer pointed position. A positive (non-zero) n affects a text running from the current pointed position to the nth following line delimiter. A negative n affects a text running from the pointer back to the beginning of the line containing the nth previous line delimiter. When n is zero, the affected text runs from the beginning of the current line to the current pointer position. N = 1 is assumed when n is omitted. - When a line command contains two numeric arguments (m,n), these represent the pointer positions between which text is affected. Except in special cases described in section 5.7, m must be less than or equal to n, or unpredictable results will occur. Standard TECO Page 3-3 Conventions and Structures When a command that normally takes an argument is specified with no argument, TECO executes the command in the most common or most useful way, as shown in the following table: Command Default Argument Default Action C 1 Advance 1 character R 1 Back over 1 character L 1 Advance 1 line J 0 Jump to start of buffer V 1 View 1 line D 1 Delete 1 character K 1 Kill 1 line S, N, etc. 1 Search for first occurrence % 1 Increment Q-register by 1 X 1 Extract one line Table 3-2 Default Arguments These default arguments reduce the number of keystrokes needed for common TECO actions. Standard TECO Page 3-4 Conventions and Structures 3.1.2 TEXT ARGUMENTS Many TECO commands take a text (character string) argument. The string is placed immediately after the command and consists of a sequence of ASCII characters terminated by an ESCAPE character (or in the case of ! and A commands, by the command character). The string of ASCII characters may not include an ESCAPE, since this would terminate the string prematurely, but may include any other character. (Some characters may be difficult to enter from a terminal because they are TECO immediate action commands or because they have been filtered out by the operating system). Examples of text arguments: Sabc$ Search for the string "abc" UAHELLO$ Insert the text "HELLO" into Q-register A OBEGIN$ Branch to the tag specified by the string "BEGIN" Some TECO commands require two text arguments. Each argument must be followed by an ESCAPE character, as follows: FSabc$def$ Replace string "abc" by "def" You can include an ESCAPE character in a text string by using another format of text argument. In this alternate form, the string is delimited on both sides by any ASCII code that does not otherwise appear in the string. You signal that this format is being used by inserting an @ character before the command, as follows: @ER5TEST.FOR5 Open the file "TEST.FOR" for input. The delimiter used is "5" @^A+Hello out there!+ Type the message "Hello out there!" on the terminal. The delimiter is "+" Unpredictable results will occur if another TECO command intervenes between an @ sign and the command that it is supposed to affect. Note that a control character used as a delimiter must be entered as . Standard TECO Page 3-5 Conventions and Structures 3.1.3 COLON MODIFIERS The colon (:) command modifies the action of the next command. In some cases, it will cause the next command to return a value indicating whether it has failed or succeeded. A zero (0) indicates that the command has failed, while a -1 indicates that it has succeeded. The colon modifier is used this way with such commands as :ER, :EB, :EN, :S, :N, :FS, :FN, :., :F., :FB, and If the next sequential command requires a positive argument, the -1 is interpreted as the largest possible positive number. :FC. In other cases, such as :Gq and :=, the colon modifier changes the meaning of the command. Unpredictable results may occur if you place a colon directly before a TECO command that does not normally accept a colon modifier. If both the : and the @ (string delimiter) are used with the same command, they may be placed in any order. Standard TECO Page 3-6 Conventions and Structures 3.2 DATA STRUCTURES A good way to begin the study of a programming language is to forget the commands, for the moment, and concentrate instead on the data structures. This section follows that approach, describing both the values on which TECO operates and the buffers and registers in which these values are stored. TECO manipulates two types of data, namely, o The character string: a sequence of zero or more ASCII characters, and o The integer: a numeric value that may be signed or unsigned. The text that TECO edits is, of course, a character string. Less obviously, the command string by which the user controls TECO is also a character string. The counters and indices for character string manipulation, and the repetition counts for loops are integers. Character strings and integers have distinct internal representation and this is reflected in the design of the TECO commands. Commands designed for character strings do not work on integers and vice versa. The data structures described in this section are frequently applied to character strings. Structure is never "built into" the data, but rather is attributed to the data by particular commands and conventions. Thus "lines" of characters are recognized by line manipulation commands, but not by character manipulation commands, which view an end-of-line character as just another ASCII code. Standard TECO Page 3-7 Conventions and Structures The following are definitions for the line and the page in TECO: o Any character string can be divided into TECO lines by considering the line to be ended by either a line feed (octal 12) a form feed (octal 14) a vertical tab (octal 13) or the end of the given character string o Any character string can be divided into TECO pages by considering the page to be ended by either a form feed (octal 14) or the end of the given character string These data structures are used to achieve two quite separate results: the formatting of type out and the logical division of data. 3.2.1 TEXT BUFFER The main storage of TECO is the text buffer. The text buffer stores a single character string that TECO edits. A text buffer pointer is used to address text in the buffer; it is moved about by many TECO commands. The text buffer pointer never points to characters in the buffer; it is always pointing at pointer positions (between characters). The available pointer positions in the text buffer are sequentially numbered beginning with 0. Pointer position 0 is the position at the start of the buffer, just to the left of the first character. Pointer position 1 is the next position, just to the right of the first character, etc. As an example, suppose the text buffer contains the string FOOBAR. Then seven text buffer pointer positions are determined as shown by the arrows in the following figure: F O O B A R _^ _^ _^ _^ _^ _^ _^ 0 1 2 3 4 5 6 Note that there are 6 characters in the buffer and that the highest numbered pointer position is 6. The pointer position number is equal to the number of characters preceding that position. Standard TECO Page 3-8 Conventions and Structures Useful definitions of "current" objects are made with respect to the text buffer pointer as follows: 1. The current character of the text buffer is the character just to the right of the pointer. If the pointer is at the end of the text buffer, there is no character to the right of the buffer pointer, and the current character does not exist. 2. The current line of the text buffer is the TECO line that contains the current character. In the special case that the pointer is at the end of the buffer, the current line is everything back to (but not including) the last end-of-line character. 3. The current page of the text buffer is the TECO page that contains the current character. In the special case that the pointer is at the end of the buffer, the current page is everything back to (but not including) the last form feed character (or the beginning of the buffer). When the text buffer pointer is at the end of the text buffer and the last character of the buffer is an end-of-line character, then the current line is an empty string according to the definition just given. In this case, TECO performs the required operation on this empty string. For example, if the pointer is at the end of the buffer and TECO is commanded to kill (delete) the next 3 lines, then the empty string is killed 3 times. Similarly, if the pointer is at the end of the buffer and TECO is commanded to advance the pointer 5 lines, the pointer will remain at the end of the buffer. No error message will be given. In a like fashion, if the pointer is at the end of the first line of the buffer, and TECO is instructed to extract the previous 4 lines (into a Q-register), then only the first line is extracted since it is presumed to be preceded by 3 empty lines. 3.2.2 Q-REGISTERS TECO provides 36 data storage registers, called Q-registers, which may be used to store single integers and/or ASCII character strings. The Q-registers have one character names: A through Z and 1 through 9. Each Q-register is divided into two storage areas. In the number storage area, each Q-register can store one signed integer. In the text storage area, each Q-register can store an ASCII character string which may be either text or a TECO command string. Various TECO commands allow the storing and retrieving of numerical values from the number storage areas of the Q-registers. Other TECO commands allow the storage and retrieval of strings from the text storage areas of the Q-registers. Standard TECO Page 3-9 Conventions and Structures 3.2.3 Q-REGISTER PUSHDOWN LIST The Q-register pushdown list is a stack that permits the numeric and text storage areas of Q-registers to be saved and restored. 3.2.4 NUMERIC VALUES AND FLAGS TECO has many special numeric values and flags which are accessible through TECO commands. Some of these values, such as the text buffer pointer, reflect the state of TECO. Others control TECO's behavior in various ways. Standard TECO Page 3-10 Conventions and Structures 3.3 SCOPE SUPPORT TECO offers three layers of scope support. 1. At the lowest level, TECO provides you with command string scope editing. This means that when you are entering a command string in reply to TECO's asterisk prompt, TECO understands about scope terminals and will do the right thing. Thus, if you are on a scope terminal and you type while entering a command string, the character to be deleted will actually be erased from the screen. If you type and the previous character was a line feed, TECO will move your terminal's cursor back up to the previous line. Deleting a will cause TECO to position the cursor at the end of the previous line on the screen. If that line had scrolled off the top of the screen, so that it is no longer visible, TECO will automatically bring the line back into view and then position the cursor at the end of that line. 2. At the intermediate level, TECO provides you with commands that allow you to display and maintain a visual "window" into the text buffer. Executing the command -1W causes the window to be updated. The window normally fills the entire screen and shows lines before and after the line currently containing the text buffer pointer. Users may write macros that monitor their progress by frequently updating the window. 3. At the highest level, TECO may invoke a video terminal editor macro which converts TECO into a "true scope editor". This macro is an editing macro that continuously updates the window and allows you to see your editing changes immediately as they occur. In this mode, typing a normal character on the terminal keyboard causes that character to be immediately entered into the text buffer and the result instantly shown in the window. Typing special keys on the terminal can move you around in the buffer (e.g. typing down arrow moves you down one line in the column you are at) or perform special functions (e.g. typing deletes the current line). There are several such video terminal editors available for TECO. One of these is called VTEDIT and is available from the DECUS program library. It is beyond the scope of this manual to describe the use of VTEDIT. There is a separate VTEDIT manual and keypad layout chart available from DECUS. Note that TECO novices and user's performing only simple editing can frequently do all their work through one of these editors, and not need to read this manual at all. Standard TECO Page 4-1 String Editing CHAPTER 4 COMMAND STRING EDITING While you are typing command strings at a terminal, TECO considers certain ASCII characters to have special meaning. Most of the special characters are immediate action commands, which cause TECO to perform a specified function immediately, instead of waiting for the double ESCAPE which terminates a command string. Immediate action commands may be entered at any point in a command string - even in the middle of a command or text argument. Many immediate action commands, such as DELETE, which deletes the immediately preceding character, cannot be used as regular TECO commands. If you enter a DELETE into a command string executed from a macro, the DELETE will not delete a character as part the execution of the command string. Some characters, like , are both regular TECO commands and immediate action commands. The command string ^Uqtext$ enters the specified text into Q-register q. However, typed while entering a command string is an immediate action command which deletes the current line. Thus you cannot type a (or any other sequence which doubles as an immediate action command) directly into TECO as part of a command string. Nevertheless, is still a valid TECO command; should TECO encounter it in a macro or indirect file, it will have its regular TECO effect (^Uqtext$). Control characters used in immediate action commands must be entered using the CONTROL key; they will not be recognized if entered as a caret or up-arrow. Tables 4-1 and 4-2 list the immediate action commands and explain their functions. Standard TECO Page 4-2 String Editing TABLE 4-1: IMMEDIATE ACTION COMMANDS These commands take immediate effect and are used to edit a command string as it is being entered: CHARACTER EXPLANATION The double character sequence tells TECO to begin execution of the command string just typed in. It echoes as $$ and also inserts two s into the command string. The two ESCAPES must be typed successively. If any other character is typed in between the two ESCAPEs (even if subsequently DELETEd), then the two ESCAPEs might be treated simply as two ESCAPEs to be entered into the command string rather than as an immediate action command. If you need to enter two ESCAPEs into a command line, as in the case where you want to use the FSstring$$ command to delete a string, you can keep TECO from recognizing $$ as an immediate action command. Type and then continue entering the remainder of your command string. A single ESCAPE character is not a special character and performs no immediate action. Typing a DELETE character (DEL or RUBOUT on some terminals) deletes the last character typed. DELETE can be typed repeatedly to erase multiple characters. TECO echoes the deleted character whenever a DELETE is typed, indicating to you that the character has been rubbed out. If you are doing your editing on a scope terminal, then the action of this key is different: the character that has been rubbed out will disappear from the screen of your editing terminal and the cursor will be moved back one position. If you delete a line feed, form feed, or vertical tab, the cursor will move up the screen and position itself at the end of the text that immediately preceded the line feed, form feed, or vertical tab. echoes as ^C (Caret-C) and aborts the entering of the command string. The exact action of the key depends on the operating system being used (See Standard TECO Page 4-3 String Editing appendices). causes the current line of the current command line to be deleted. TECO echoes the character as ^U followed by and an asterisk prompt. If you are using a scope terminal, the visible action of typing this key is different. The current line physically disappears from the screen and the cursor is positioned back at the beginning of the line. Typing two consecutive characters causes all commands which have been entered but not executed to be erased. (If the terminal has a bell, it will ring.) This command is used to erase an entire command string. A single character is not a special character. followed by a space causes the line currently being entered into the command string to be retyped. * followed by an asterisk causes all the lines typed by the user from the last TECO prompt (the asterisk) to be retyped. Typing a carriage return enters a carriage return followed by a line feed into the command string. To enter a carriage return without a line feed, type . RSX-11 TECO uses the triple command as an immediate action command. See the appropriate appendix for more details. The character is used as an end-of-file terminator in some contexts on some operating systems. While its presence is usually harmless in disk files, it may cause premature end of file if the file is copied to other media (e.g., paper tape). Standard TECO Page 4-4 String Editing TABLE 4-2: IMMEDIATE ACTION AIDS These immediate action commands are aids to the user. They have special meaning and take immediate effect only if they are typed as the very first keystroke after TECO's asterisk prompt. CHARACTER EXPLANATION ? If the previous command aborted because of an error, this immediate action command causes TECO to print the erroneous command string from the beginning of the current macro level up to and including the character that caused the error. / If TECO has just printed an error message, type this immediate action command to receive a more detailed explanation of the error. [Not in TECO-11] Typing this immediate action command, line feed, as the first keystroke after TECO's prompt causes TECO to immediately execute the LT command. This aid lets you "walk through" a file on a non-scope terminal. (If the EV flag is non-zero, then the T portion of this command is redundant and therefore is not performed.) Note that on TECO-11, this command has no effect when the text buffer pointer is at the end of the text buffer. [Not in TECO-10] Typing this immediate action command, backspace, (as the first keystroke after TECO's prompt) causes TECO to immediately execute the -LT command. (If the EV flag is non-zero, then the T portion of this command is redundant and therefore is not performed.) Note that in TECO-11, this command has no effect when the text buffer pointer is at the beginning of the text buffer. [Not in TECO-10] *q When an asterisk followed immediately by a Q-register name (any alphanumeric character, here represented by q) is the first keystroke after TECO's prompt, TECO places the previous command string into Q-register q. [In TECO-8, only the *z command is permitted, and TECO will automatically type the z.] Note that since *q is itself an immediate action command, it may not be edited with other immediate action commands. In other words, you can't use DELETE to delete an incorrectly typed *. [In TECO-10, *q must be followed by .] Standard TECO Page 4-5 String Editing Although TECO accepts all 128 characters of the 7-bit ASCII character set, whether encountered in a macro, or entered directly into a command string from the terminal, some operating systems filter out certain characters typed at a terminal and do not pass them to TECO. So that you can be aware of the possible difficulty of entering these characters directly into a TECO command string, we list them below in Table 4-3. Note that these characters are still valid characters to TECO, but must be entered indirectly, such as by by entering them into a macro using the nI$ command. TABLE 4-3: OPERATING SYSTEM CHARACTER FILTERS SYSTEM CHARACTER SYSTEM's USE RT-11 ^A VT11 support [only if GT ON] ^B Background control [F/B systems only] ^E VT11 support [only if GT ON] ^F Foreground control [F/B systems only] ^O output control ^Q Terminal Synchronization RSTS/E ^O output control ^Q Terminal Synchronization ^S Terminal Synchronization VAX/VMS ^O output control ^Q Terminal Synchronization ^S Terminal Synchronization ^X Cancel Type-ahead ^Y Process Interruption RSX-11 ^O output control ^Q Terminal synchronization ^S Terminal synchronization ^X Task control (RSX-11D only) TOPS-10 ^C^C Job interruption ^O output control ^Q Terminal synchronization ^S Terminal synchronization ^T System status TOPS-20 ^C^C Job interruption ^O output control ^Q Terminal synchronization ^S Terminal synchronization ^T System status OS/8 ^B Background control [F/B systems only] ^F Foreground control [F/B systems only] ^Y Reboot indicator [F/B systems only] Standard TECO Page 4-6 String Editing Standard TECO Page 5-1 Logical Command Summary CHAPTER 5 LOGICAL COMMAND SUMMARY This chapter presents a detailed description of the full TECO command set, functionally organized. It assumes that the reader is familiar with the elementary TECO commands presented earlier. In the sections following, the letters "m" and "n" are used in command formats to represent numerical arguments. These may be either simple integers or complex expressions. The letter "q" represents any Q-register. Standard TECO Page 5-2 File Selection Commands 5.1 FILE SPECIFICATION COMMANDS You must specify an input file whenever you want TECO to accept text from any source other than the terminal. You must specify an output file whenever you want to make a permanent change to the input file. Input and output files are selected by means of file specification commands. File specification formats are operating system dependent and are fully described in the operating characteristics appendices at the end of this manual. Almost every editing job begins with at least one file specification command. Additional file specification commands may be executed during an editing job whenever required; however, TECO will keep only one input file and one output file selected at a time. TECO-11 recognizes two input and two output "streams" called the primary and secondary streams. The primary input and output streams are initially selected when TECO is invoked. Most file selection commands, and all of the other TECO commands (page manipulation, etc.), operate on the currently selected input and/or output stream. Table 5-1 lists all of the file specification commands. Unless otherwise noted, all of these commands leave the text buffer unchanged. Examples of some of these commands appear in Chapter 1. Standard TECO Page 5-3 File Selection Commands TABLE 5-1A: FILE SPECIFICATION COMMANDS COMMAND FUNCTION EBfilespec$ Edit Backup. This command is recommended for most editing jobs. It is used for files on file-structured devices only. It opens the specified file for input on the currently selected input stream and for output on the currently selected output stream. The EB command also keeps the unmodified file (the latest copy of the input file) available to the user; details of this process are system dependent (See appendices). ERfilespec$ Edit Read. Opens a file for input on the currently selected input stream. EWfilespec$ Edit Write. Opens a file for output on the currently selected output stream. :EBfilespec$ Executes the EB command, and returns a numeric value. -1 returned indicates success: the file is open for input. A 0 indicates the specified file could not be found, and no error message is generated. Other errors (e.g., hardware errors, protection violations, etc.) generate messages and terminate command execution as usual. :ERfilespec$ Executes the ER command, and returns a numeric value. See the :EB command, above. Standard TECO Page 5-4 File Selection Commands Various system-dependent switches (qualifiers) of the form /SWITCH can be used with the file specification in ER, EW, and EB commands. These switches are described below: TABLE 5-1B: SWITCHES ON FILE SPECIFICATIONS System Switch Meaning OS/8 /S Ignore end-of-file (s) on input. (SUPER TECO mode) RSTS/E /B Read and write with unfiltered 8-bit /B+ Handle a BASIC-PLUS file /B2 Handle a BASIC-PLUS-2 file /CLUSTERSIZE:n Specifies output file cluster size /MODE:n Use non-standard open mode /n Handle BASIC-PLUS continuation character (&) in column n RSX-11 VAX/VMS /B2 Handle a BASIC-PLUS-2 file /CR Implied carriage control /-CR No (internal) carriage control /FT FORTRAN carriage control /RW Rewind magtape before opening file /SH Open the file in shared mode TOPS-10 /APPEND Append to existing output file (EW only) /ASCII File is ASCII /GENLSN Generate line sequence numbers /NOIN Don't put user type-in into log file /NONSTD Open DECtape in non-standard mode /NOOUT Don't put TECO's type out into log file (EL only) /OCTAL Read file in octal /PROTECT:n Specify protection code /SIXBIT Read file in pure SIXBIT /SUPLSN Suppress line sequence numbers Standard TECO Page 5-5 File Selection Commands The following commands are used to close files and exit from TECO: TABLE 5-1C: FILE EXIT AND CLOSE EC Moves the contents of the text buffer, plus the remainder of the current input file on the currently selected input stream, to the current output file on the currently selected output stream; then closes those input and output files. Control remains in TECO. EC leaves the text buffer empty. EF Closes the current output file on the currently selected output stream. The EF command does not write the current contents of the buffer to the file before closing it. EG$ Performs the same function as the EX command, but then exits from TECO and re-executes the last COMPIL class command (.COMPILE, .LINK, .EXECUTE, etc.) [Not in TECO-11] EGtext$ Performs the same function as the EC command, but then exits from TECO and passes "text" to the operating system as a command string to be executed (see appendices). :EGtext$ Performs the same function as the EC command, and then performs an operating system specific function. Consult the appendices for details. Returns -1 for success, 0 for failure. EK Kill the current output file on the currently selected output stream. This command, which purges the output file without closing it, is useful to abort an undesired edit. Executing the EK command after an EW which is superseding an existing file leaves the old file intact. The EK command also "undoes" an EB command. (See appendices for details.) ELfilespec$ Open the specified file for output as a log file. Any currently open log file will be closed. If the /APPEND switch is given, future logs will append to the file (if it already exists). The default is to supersede. All type-in to TECO and all type out from TECO goes into the log file. The log file is automatically closed by the EX and TECO commands. [TECO-10 only] Standard TECO Page 5-6 File Selection Commands EX Performs the same function as the EC command, but then exits from TECO. For safety reasons, this command is aborted if there is text in the text buffer but no output file is open. EZfilespec$ This command is useful for outputting to magtapes and DECtapes, on which it initializes (zeros) the specified output device before switching the ouput to the primary output stream. In the case of a magtape, this command rewinds the magtape to load point. If the output device is a disk, this command works exactly like the EW command. [TECO-10 only] The (caret/C) command terminates execution of the current command string and returns control to TECO's prompt. (Under TECO-8, the command currently acts as .) The ^C command causes an immediate abort and exit from TECO. Currently open files are not necessarily closed. See the appendices for more details. Note that the second may not be entered in up-arrow mode. Standard TECO Page 5-7 File Selection Commands The following commands manipulate the secondary input and output streams: SECONDARY STREAM COMMANDS [Not in TECO-8, TECO-10, or RT-11] Input commands (do not open or close any file; do not change the text buffer): EP Switches the input to the secondary input stream. ER$ Switches the input to the primary input stream. Output commands (do not open or close any file; do not change the text buffer): EA Switches the output to the secondary output stream. EW$ Switches the output to the primary output stream. Indirect file commands: EIfilespec$ Opens a file as an indirect command file, so that any further TECO requests for terminal input will come from this file. At end-of-file, or upon TECO's receipt of any error message, the indirect command file will be closed and terminal input will be switched back to the terminal. Note that this command only presets where input will come from; it does not "splice" the file's data into the current command string. While end-of-file closes the indirect command file, it does not automatically start execution of commands. Execution will begin only upon TECO's receipt of two adjacent ESCAPEs. All commands encountered in the indirect file will have their normal TECO meaning (as opposed to any immediate action meaning). For example, a encountered in an indirect file will not erase the command line in which it occurs. Instead, it will be treated as the TECO ^Uqtext$ command. The only exception to this rule is the command, which directs TECO to execute the preceding command string and then return to the indirect file at the point following the . Standard TECO Page 5-8 File Selection Commands EI$ If an indirect command file is active, this command will close it and resume terminal input from the terminal. Any portion of the file after a double ESCAPE which has not yet been read is discarded. This command has no effect if no indirect file is already open. Standard TECO Page 5-9 File Selection Commands TECO-11 supports wild card file processing with a set of special commands, to allow TECO programs to operate on a set of files. WILDCARD COMMANDS [Not in TECO-8, TECO-10, or RT-11] ENfilespec$ This command presets the "wild card" lookup filespec. It is only a preset; it does not open, close, or try to find any file. The "wild card" lookup is the only filespec that can contain any wild card notations. See the appendices for the allowed wild fields in each operating system. EN$ Once the wild card lookup filespec has been preset, executing this command will find the next file that matches the preset wild card lookup filespec and will load the filespec buffer with that file's name. The G* command (see *****) can be used to retrieve the fully expanded filespec. When no more occurences of the wild card filespec exist, the ?FNF error is returned. :EN$ Executes the EN$ command, and returns a numeric value. A -1 indicates that another match of the wild card filespec exists and has been loaded into the filespec buffer. A 0 indicates no more occurences exist. No error message is generated. The filespec argument to the file selection commands in TECO-11 can use the string building characters described in Table 5-8A (see section 5.8). The Q* construct, described in Appendix C, is especially useful in TECO-11. Standard TECO Page 5-10 File Selection Commands TECO-10 provides commands to do I/O directly to and from the Q-registers, allowing I/O to bypass the text buffer. DIRECT I/O TO Q-REGISTERS EQqfilespec$ Read specified file into Q-register q. No s or s are removed from the file, except that trailing s are discarded. The only switch permitted on the filespec in this command is the /DELETE switch, which causes TECO to delete the file after reading it, providing that the file is less than 500 characters long. This command supports the pseudo-device TMP:, for TMPCOR. Consult the appropriate appendix for details. [TECO-10 only] E%qfilespec$ Create the specified file. The contents of the file will be the contents of Q-register q with no s deleted. No switches are permitted on the filespec of this command. This command supports the pseudo-device TMP:, for TMPCOR. Consult the appropriate appendix for details. [TECO-10 only] Standard TECO Page 5-11 Page Manipulation Commands 5.2 PAGE MANIPULATION COMMANDS The following commands permit text to be read into the text buffer from an input file or written from the buffer onto an output file. All of the input commands listed in this table assume that the input file is organized into pages small enough to fit into available memory. If any page of the input file contains more characters than will fit into available memory, the input command will continue reading characters into the buffer until a line feed is encountered when the buffer is two thirds full. See the appendices for more details. Special techniques for handling pages larger than the buffer capacity will be presented later in this chapter. TABLE 5-2: PAGE MANIPULATION COMMANDS COMMAND FUNCTION APPEND commands: A Appends the next page of the input file to the contents of the text buffer, thus combining the two pages of text on a single page with no intervening form feed character. This command takes no argument. To perform n Appends, use the n construct. Note that nA is a completely different command. :A Equivalent to the A command except that a value is returned. -1 is returned if the append succeeded, and 0 is returned if the append failed because the end-of-the-input-file had previously been reached (^N flag is -1 at start of this command). [Not in TECO-8] n:A Appends n lines of text from the input file to the contents of the text buffer. A value is returned indicating whether or not there were in fact n lines remaining in the input file. -1 is returned if the command succeeded. 0 is returned if end-of-file on the input file was encountered before all n lines were read in. Note that the command can succeed and yet read in fewer than n lines in the case that the text buffer fills up. [Not in TECO-8] PAGE Commands: P Writes the contents of the buffer onto the output file, then clears the buffer and reads the next page of the input file into the buffer. A form feed is appended to the output file if the last page read in (with a P, Y, Standard TECO Page 5-12 Page Manipulation Commands or A command) was terminated with a form feed. :P Same as the P command except that a value is returned. -1 is returned if the command succeeded. 0 is returned if the command failed because the end-of-file on the input file had been reached prior to the initiation of this command. [Not in TECO-8] nP Executes the P command n times, where n must be a non-zero positive integer. PW Write the contents of the buffer onto the output file and append a form feed character. The buffer is not cleared and the pointer position remains unchanged. nPW Executes the PW command n times, where n must be a non-zero positive integer. m,nPW Writes the contents of the buffer from the m+1th character through and including the nth character onto the output file. m and n must be positive integers and m should be less than n. A form feed is not appended to this output, nor is the buffer cleared. The pointer position remains unchanged. m,nP Equivalent to m,nPW. HPW Equivalent to the PW command except that a form feed character is not appended to the output. (See Section 5.11 for the definition of H.) HP Equivalent to HPW. YANK commands: Y Clears the text buffer and then reads the next page of the input file into the buffer. As the Y command can result in the loss of data, it is not permitted under certain circumstances (see ED flag in 5.14). :Y Same as the Y command but a value is returned. -1 is returned if the Yank succeeded. 0 is returned if the Yank failed because the end-of-file had been reached on the input file prior to the initiation of this command. [Not in TECO-8] EY Same as the Y command, but it will always succeed since its action is not dependent on the value of the Yank Protection bit in the ED flag. :EY Same as the :Y command, but it will always succeed since its action is not dependent on the value of the Yank protection bit in the ED flag. [Not in TECO-8] Standard TECO Page 5-13 Buffer Pointer Manipulation Commands 5.3 BUFFER POINTER MANIPULATION COMMANDS Table 5-3 describes all of the buffer pointer manipulation commands These commands may be used to move the pointer to a position between any two characters in the buffer, but they will not move the pointer across a buffer boundary. If any R or C command attempts to move the pointer backward beyond the beginning of the buffer or forward past the end of the buffer, the command is ignored and an error message is printed. If any L command attempts to exceed the buffer boundaries, the pointer is positioned at the boundary which would have been exceeded and no error message is printed. TABLE 5-3: BUFFER POINTER MANIPULATION COMMANDS COMMAND FUNCTION CHARACTER commands: C Advances the pointer forward across one character. nC Executes the C command n times. If n is positive, the pointer is moved forward across n characters. If n is negative, the pointer is moved backward across n characters. If n is zero, the pointer position is not changed. n:C Same as nC except that a value is returned. If the command succeeded, -1 is returned. If the command failed, the pointer does not move and a value of 0 is returned. [TECO-10 only] :C Equivalent to 1:C. -C Equivalent to -1C. JUMP commands: J Moves the pointer to a position immediately preceding the first character in the buffer. Equivalent to 0J. nJ Moves the pointer to a position immediately following the nth character in the buffer. ZJ Moves the pointer to a position immediately following the last character in the buffer. n:J Same as the nJ command except that if pointer position n is outside of the buffer, the pointer does not move and a value of 0 is returned. If the command succeeded, a value of -1 is returned. [TECO-10 only] Standard TECO Page 5-14 Buffer Pointer Manipulation Commands LINE commands: L Advances the pointer forward across the next line terminator (line feed, vertical tab, or form feed) and positions it at the beginning of the next line. nL Executes the L command n times. A positive value of n advances the pointer to the beginning of the nth line following its current position. A negative value of n moves the pointer backwards to the beginning of the nth complete line preceding its current position. If n is zero, the pointer is moved to the beginning of the line on which it is currently positioned. -L Equivalent to -1L. REVERSE commands: R Moves the pointer backward across one character. nR Executes the R command n times. If n is positive, the pointer is moved backward across n characters. If n is negative, the pointer is moved forward across n characters. If n is zero, the position of the pointer is not changed. -R Equivalent to -1R. n:R Same as the nR command except that a value is returned. If the command succeeded, then a value of -1 is returned. If the command failed, then the buffer pointer is not moved and a value of 0 is returned. [TECO-10 only] :R Equivalent to 1:R. Standard TECO Page 5-15 Text Type Out Commands 5.4 TEXT TYPE OUT COMMANDS Table 5-4 describes the commands used to type out part or all of the contents of the buffer for examination. These commands do not move the buffer pointer. TABLE 5-4: TEXT TYPE OUT COMMANDS COMMAND FUNCTION T Types out the contents of the buffer from the current position of the buffer pointer through and including the next line terminator character. nT Types n lines. If n is positive, types the n lines following the current position of the pointer. If n is negative, types the n lines preceding the pointer. If n is zero, types the contents of the buffer from the beginning of the line on which the pointer is located up to the pointer. -T Equivalent to -1T. m,nT Types out the contents of the buffer from the m+1th character through and including the nth character in the buffer. M should be less than n. .,.+nT Types out the n characters immediately following the buffer pointer. N should be greater than zero. (See 5.11 for the definition of .) .-n,.T Types the n characters immediately preceding the buffer pointer. N should be greater than zero (i.e., -n should be less than zero). n^T Types out the character whose ASCII code is n. This can be used to output any ASCII character to the terminal. HT Types out the entire contents of the buffer. V Types out the current line. Equivalent to 0TT. nV Types out n-1 lines on each side of the current line. Equivalent to 1-nTnT. [Not in TECO-8] m,nV Types out m-1 lines before the current line and n after. Equivalent to 1-mTnT. [Not in TECO-8.] Standard TECO Page 5-16 Text Type Out Commands ^Atext Types "text" on the terminal. While the command may begin with or Caret/A, the closing character must be a . A numeric argument must not be specified with this command. @^A/text/ Equivalent to the ^A command except that the text to be printed may be bracketed with any character. This avoids the need for the closing . Standard TECO Page 5-17 Text Type Out Commands You may stop or delay the output of any type out command by typing certain special charactes at the keyboard while TECO is typing out at the terminal (via a T, V, ^A, or :G command). These characters are described in the table below: TABLE 5-4B: TYPE OUT TIME COMMANDS CHARACTER FUNCTION Stops the terminal output of the current command string. TECO continues to run and to send characters to the terminal, however, these characters are suppressed from actually printing on the terminal. You can resume printing characters by typing another while type out is being suppressed. TECO cancels this suppression the next time that it prompts for command string input. A TECO macro can cancel the effect of any by setting the 16's bit in the ET flag (see section 5.16). Freezes the terminal output of the current command string. TECO stops running the next time it tries to output a character to your terminal, and waits for you to type a to indicate that output should resume. Causes TECO to resume any type out that was frozen via use of the command described above. This character has this effect only while typout is frozen. Striking any key other than or while type out is frozen will have unpredictable results; consult the appropriate operating system manual. Note that , , and are legal TECO commands as well. When TECO is not typing on the terminal (when you are entering a command string, for example), these characters do not have the effect described above. They may be entered into your command string just like any other control character (except under operating systems that filter out these characters). Standard TECO Page 5-18 Deletion Commands 5.5 DELETION COMMANDS Table 5-5 summarizes the text deletion commands, which permit deletion of single characters, groups of adjacent characters, single lines, or groups of adjacent lines. TABLE 5-5: TEXT DELETION COMMANDS COMMAND FUNCTION DELETE commands: D Delete the first character following the current position of the buffer pointer. nD Execute the D command n times. If n is positive, the n characters following the current pointer position are deleted. If n is negative, the n characters preceding the current pointer position are deleted. If n is zero, the command is ignored. -D Equivalent to -1D. m,nD Equivalent to m,nK. [TECO-11 only] n:D Same as nD but returns a value (-1 if command succeeds, 0 if command failed because the range of characters to be deleted fell outside the text buffer). [TECO-10 only] FDtext$ Same as FStext$$ [TECO-10 only] @FD// Equivalent to FDtext$ except that the character is not necessary. FR$ Equivalent to -nD where n is the length of the last insert, get or search command. See the description of the FRtext$ command in section 5.6 for more details. @FR// Form of the FR$ command that does not require use of the character. KILL commands: K Deletes the contents of the buffer from the current position of the buffer pointer through and including the next line terminator character. nK Executes the K command n times. If n is positive, the n lines following the current pointer position are deleted. If n is negative, the n lines preceding the Standard TECO Page 5-19 Deletion Commands current pointer position are deleted. If n is zero, the contents of the buffer from the beginning of the line on which the pointer is located up to the pointer is deleted. It is not an error if more lines are specified than occur when a boundary of the text buffer is encountered. -K Equivalent to -1K. m,nK Deletes the contents of the buffer from the m+1th character through and including the nth character. M should be less than n. The pointer moves to position m. The ?POP error message (or its equivalent) is issued if either m or n is out of range. .,.+nK Equivalent to nD. Deletes the n characters immediately following the buffer pointer. N should be greater than zero. .-n,.K Equivalent to -nD. Deletes the n characters immediately preceeding the buffer pointer. N should be greater than zero. FKtext$ Executes a Stext$ command then deletes all the text from the initial pointer position to the new pointer position. [TECO-10 only] @FK/text/ Equivalent to FKtext$ except that "text" may contain any character, including , other than the delimiter (shown here as /). [TECO-10 only] HK Deletes the entire contents of the buffer. Standard TECO Page 5-20 Insertion Commands 5.6 INSERTION COMMANDS Table 5-6 lists all of the text insertion commands. These commands cause the string of characters specified in the command to be inserted into the text buffer at the current position of the buffer pointer. Following execution of an insertion command, the pointer will be positioned immediately after the last character of the insertion. The length of an insertion command is limited primarily by the amount of memory available for command string storage. During normal editing jobs, it is most convenient to limit insertions to about 10 or 15 lines each. When command string space is about to run out, TECO will ring the terminal's bell after each character that is typed. From the time you hear the first warning bell, you have 10 characters to type in order to clean up your command line. Attempting to enter too many characters into the current command string causes unpredictible results to occur and should be avoided. Use the DELETE key to shorten the command to permit its termination. As explained above in Chapter 4, certain characters are filtered out by the operating system and/or may perform special functions, and some characters are immediate action commands and have special effect. If you want to insert such characters into the text buffer, use the nI$ command described in the following table. It will insert any ASCII character into the buffer, including the special characters that could not ordinarily be typed at a terminal. TABLE 5-6: TEXT INSERTION COMMANDS COMMAND FUNCTION INSERT commands: Itext$ Where "text" is a string of ASCII characters terminated by an ESCAPE, the specified text string is entered into the buffer at the current position of the pointer, with the pointer positioned immediately after the last character of the insertion. nI$ This form of the I command inserts the single character whose 7-bit ASCII code is n into the buffer at the current position of the buffer pointer. (n is taken modulo 128.) nI$ is used to insert characters that are not available on the user's terminal or special characters such as DELETE which may not be inserted from a terminal with the standard I command @I/text/ Equivalent to the I command except that the text to be inserted may contain ESCAPE characters. A delimiting character (shown as a slash here) must precede and Standard TECO Page 5-21 Insertion Commands follow the text to be inserted, as described in Section 3.1.2 above. n@I// Equivalent to the nI$ command, but does not require the ESCAPE character. FRtext$ Equivalent to "-nDItext$", where "n" is obtained from the most recent occurrence of the following: (a) the length of the most recent string found by a successful search command, (b) the length of the most recent text string inserted (including insertions from the FS, FN, or FR commands), or (c) the length of the string retrieved by the most recent "G" command. In effect, the last string inserted or found is replaced with "text", provided that the pointer has not been moved. [Not in TECO-8] @FR/text/ Equivalent to "FRtext$", except that "text" may contain ESCAPE characters. [Not in TECO-8] text$ This command is equivalent to the I command except that the is part of the text which is inserted into the buffer. Standard TECO Page 5-22 Search Commands 5.7 SEARCH COMMANDS In many cases, the easiest way to position the buffer pointer is by means of a character string search. Search commands cause TECO to scan through text until a specified string of characters is found, and then position the buffer pointer at the end of the string. A character string search begins at the current position of the pointer. It proceeds within the current buffer in a forward or a reverse direction or through the file in a forward direction. Specifying a negative numeric argument to the search command causes the search to proceed backwards from the pointer. Your last explicitly specified search string is always remembered by TECO. If a search command is specified with a null search string argument, the last explicitly defined search string will be used. This saves having to retype a complex or lengthy search string on successive search commands. Normally searches are "unbounded" - they search from the current position to the end of the text buffer (or in the case of backwards searches, until the beginning of the buffer. A bounded search, however, will only search from the current position to the specified bound limit. If the search string is found within the bound limits, the pointer is positioned immediately after the last character in the string. If the string cannot be found, the pointer is left unchanged. A special case of the bounded search occurs when the upper and lower bound limits are the same. In such a case, the search command is called an anchored search, and is used to compare the search argument against the character string immediately following the text buffer pointer. TECO-8 does not permit backward searches, bounded searches, or anchored searches. This is a general property and will not be specifically mentioned again in the following tables. TABLE 5-7A: SEARCH COMMANDS Stext$ Where "text" is a string of characters terminated by an ESCAPE. This command searches the text buffer for the next occurrence of the specified character string following the current position of the buffer pointer. If the string is found, the pointer is positioned after the last character in the string. If it is not found, the pointer is positioned immediately before the first character in the buffer (i.e., a 0J is executed) and an error message is printed. nStext$ This command searches for the nth occurrence Standard TECO Page 5-23 Search Commands of the specified character string, where n is greater than zero. It is identical to the S command in other respects. -nStext$ Identical to "nStext$" except that the search proceeds in the reverse direction. If the string is not found, the pointer is positioned immediately before the first character in the buffer and an error message is printed. If the pointer is positioned at the beginning of or within an occurrence of the desired string, that occurrence is considered to be the first one found and the pointer is positioned after the last character in the string. -Stext$ Equivalent to -1Stext$. Ntext$ Performs the same function as the S command except that the search is continued across page boundaries, if necessary, until the character string is found or the end of the input file is reached. This is accomplished by executing an effective P command after each page is searched. If the end of the input file is reached, an error message is printed and it is necessary to close the output file and re-open it as an input file before any further editing may be done on that file. The N command will not locate a character string which spans a page boundary. nNtext$ This command searches for the nth occurrance of the specified character string, where n must be greater than zero. It is identical to the N command in other respects. _text$ The underscore command is identical to the N command except that the search is continued across page boundaries by executing effective Y commands instead of P commands, so that no output is generated. Since an underscore search can result in the loss of data, it is aborted under the same circumstances as the Y command (see the ED flag in section 5.16). Note that underscore is backarrow on some terminals. n_text$ This command searches for the nth occurrence of the specified character string, where n must be greater than zero. It is identical to the _ command in other respects. E_text$ Same as _text$ command except that effective Standard TECO Page 5-24 Search Commands EY (rather than Y) commands are used. Thus, this command is never aborted and is not controlled by the Yank protection bit in the ED flag. nE_text$ Same as n_text$ command except that effective EY (rather than Y) commands are used. TABLE 5-7B: BOUNDED SEARCH COMMANDS m,nStext$ System specific command. Consult Appendix C. m,nFBtext$ Performs the same function as the nStext$ command, but m and n (inclusive) serve as bounds for the search. In order for a search to be successful, the first character to match must occur between buffer pointer positions m and n. The string that is matched is permitted to extend beyond the search limits specified, provided that it begins within bounds. If mn, then the search proceeds in the reverse direction. nFBtext$ Performs a bounded search over the next n lines. If n is positive, the search proceeds forward over the next n lines; if n is negative the search proceeds backwards over the n preceding lines; if n is zero, the search proceeds backwards over the portion of the line preceding the pointer. FBtext$ Equivalent to 1FBtext$. -FBtext$ Equivalent to -1FBtext$. ::Stext$ Compare command. The ::S command is not a true search. If the characters in the buffer immediately following the current pointer position match the search string, the pointer is moved to the end of the string and the command returns a value of -1; i.e., the next command is executed with an argument of -1. If the characters in the buffer do not match the string, the pointer is not moved and the command returns a value of 0. Identical to ".,.:FBtext$". Standard TECO Page 5-25 Search Commands The search and replace commands listed below perform equivalent functions to the search commands listed next to them, but then delete "text1" and replace it with "text2". TABLE 5-7C: SEARCH AND REPLACE COMMANDS Search & Replace Search Command FStext1$text2$ Stext1$ nFStext1$text2$ nStext1$ FNtext1$text2$ Ntext1$ nFNtext1$text2$ nNtext1$ F_text1$text2$ _text1$ [not in TECO-10] nF_text1$text2$ ntext1$ [Not in TECO-10] FCtext1$text2$ FBtext1$ nFCtext1$text2$ nFBtext1$ m,nFCtext1$text2$ m,nFBtext1$ In addition, the four following commands can be used on TECO-10: FDtext$ Identical to the "FStext$$" command. [TECO-10 only] nFDtext$ Identical to the "nFStext$$" command. [TECO-10 only] nFKtext$ Searches for the nth following occurrence of "text" and then deletes all characters in the text buffer between the pointer positions before and after the search. [TECO-10 only] FKtext$ Equivalent to 1FKtext$ [TECO-10 only] The FS, F_, and FN commands above can also be reverse searches (n<0) or bounded searches (m,n argument). A reverse F_ or FN acts like a reverse S; that is the search terminates when the beginning of the text buffer is encountered. Standard TECO Page 5-26 Search Commands If a search command is entered without a text argument, TECO will execute the search command as though it had been entered with the same character string argument as the last search command entered. For example, suppose the command "STHE END$" results in an error message, indicating that character string "THE END" was not found on the current page. Entering the command "N$" causes TECO to execute an N search for the same character string. Although the text argument may be omitted, the command terminator (ESCAPE) must always be entered. Search commands can make use of the colon modifier described in Chapter 3. The following examples illustrate use of the colon modifier: COMMANDS: n:Stext$ m,n:Stext$ n:Ntext$ n:_text$ n:FStext1$text2$ m,n:FStext1$text2$ n:FNtext1$text2$ etc. FUNCTION: In each case, execute the search command. If the search is successful, execute the next sequential command with an argument of -1. If the search fails, execute the next command with an argument of zero. If the next command does not require a numeric argument, execute it as it stands. All search commands may also use the @ modifier to use alternate delimiters, to allow characters in search strings or to avoid the use of characters in command strings. Such search commands take the following forms: COMMANDS: @S/text/ m,n@FB/text/ n@FS/text1/text2/ @:N/text/ etc. Standard TECO Page 5-27 Search Arguments 5.8 SEARCH ARGUMENTS TECO builds the search string by loading its search string buffer from the supplied search command argument. To help you enter special characters or frequently used character sequences, the argument may contain special string building characters. Table 5-8A lists the string building characters and their functions. TECO-8 does not support the extended String Build functions or Match Control Constructs that begin with . This is a general property and will not be repeated in the following tables. Note that, as explained in Chapter 3, a caret (up-arrow) may be used to indicate that the character following it is to be treated as a control character. Any of the commands below may be entered using the caret. This function of the caret can be disabled by using the ED flag (see 5.16 and appendices). TABLE 5-8A: STRING BUILDING CHARACTERS CHARACTER FUNCTION A character in a search command argument indicates that the character following the is to be used literally rather than as a match control character. Same as . A character in a search command argument indicates that the character following the is to be used as the equivalent character in the lower case ASCII range (i.e., octal 100 to 137 is treated as octal 140 to 177). Two successive characters in a string argument indicate to TECO that all following alphabetic characters in this string are to be converted to lower case unless an explicit ^W is given to override this state. This state continues until the end of the string or until a ^W^W construct is encountered. [TECO-10 only] A character in a search command argument indicates that the character following the is to be used as the equivalent character in the upper case ASCII range (i.e., octal 140 to 177 is treated as octal 100 to 137). Standard TECO Page 5-28 Search Arguments Two successive characters indicates to TECO that all following alphabetic characters in this string are to be converted to upper case unless an explicit ^V is encountered to override this state. This state continues until the end of the string or until a ^V^V construct is encountered. [TECO-10 only] Qq Qq indicates that the string stored in Q-register q is to be used in the position occupied by the ^EQq in the search string. Q registers are discussed in section 5.9 below. [Not in TECO-10] Uq Uq indicates that the character whose ASCII code is specified by the numeric storage area of Q-register q is to be used in the position occupied by the ^EUq in the search string. [TECO-11 only] String build characters are also permitted inside the string arguments of the O, EB, ER, EW, and EG commands. TECO executes a search command by attempting to match the search command argument character-by-character with some portion of the input file. There are several special control characters that may be used in search command arguments to alter the usual matching process. Table 5-8B lists these match control characters and their functions. TABLE 5-8B: MATCH CONTROL CHARACTERS CHARACTER FUNCTION A character indicates that this position in the character string may be any character. TECO accepts any character as a match for . A character indicates that any separator character is acceptable in this position. TECO accepts any character that is not a letter (upper or lower case A to Z) or a digit (0 to 9) as a match for . TECO accepts any character as a match for the character combination EXCEPT the character which follows the . can be combined with other special characters. For example, the combination D means Standard TECO Page 5-29 Search Arguments match anything except a digit in this position. A A indicates that any alphabetic character (upper or lower case A to Z) is acceptable in this position. B Same as . C C indicates that any character that is legal as part of a symbol constituent is acceptable in this position. TECO accepts any letter (upper or lower case A to Z), any digit (0 to 9), a dot (.), or a dollar sign ($) as a match for C. Additional characters may be matched depending upon the operating system; consult the appropriate appendix. D D indicates that any digit (0 to 9) is acceptable in this position. Gq Gq indicates that any character contained in Q-register q is acceptable in this position. For example, if Q-register A contains "A*:" then TECO accepts either A, *, or : as a match for GA. [Not in TECO-10] L L indicates that any line terminator (line feed, vertical tab, or form feed) is acceptable in the position occupied by L in the search string. M M indicates that any number of occurrences of the immediately following character or match control construct is acceptable at this position. [TECO-10 only] R R indicates that any alphanumeric character (letter or digit as defined above) is acceptable in this position. S S indicates that any non-null string of spaces and/or tabs is acceptable in the position occupied by S. V V indicates that any lower case alphabetic character is acceptable in this position. W W indicates that any upper case alphabetic character is acceptable in this position. X Equivalent to . indicates that the character whose Standard TECO Page 5-30 Search Arguments ASCII octal code is nnn is acceptable in this position. [TECO-10 only] [a,b,c,...] [a,b,c,...] indicates that any one of the specified characters is acceptable in this position. One or more characters or other match control constructs are permitted. [TECO-10 only] TECO-8 uses special symbols to represent certain match control characters when they are displayed by an error message. These display symbols are: Character Display N S X Standard TECO Page 5-31 Q-registers 5.9 Q-REGISTERS TECO provides 36 data storage registers, called Q-registers, which may be used to store single integers and/or ASCII character strings. Each Q-register is divided into two storage areas: a number storage area and a text storage area. The number storage area can store one signed integer. The text storage area can store an ASCII character string which may be either text or a TECO command string. Each Q-register has a single character name which is one of the letters A to Z or one of the digits 0 to 9. Upper and lower case letters may be used interchangeably. TECO-10 allows additional Q-registers besides the 36 described above. Consult Appendix C for further details. Table 5-9A lists the commands which permit characters to be loaded into the Q-registers. TABLE 5-9A: Q-REGISTER LOADING COMMANDS COMMAND FUNCTION ^Uqstring$ This command inserts character string "string" into the text storage area of Q-register q. When entering a command string from the terminal, you must specify ^U using the caret/U format, since the character is the line erase immediate action command. :^Uqstring$ This command appends character string "string" to the text storage area of Q-register "q". n^Uq$ This form of the ^Uq$ command inserts the single character whose 7-bit ASCII code is n into the text storage area of Q-register "q". n:^Uq$ This form of the :^Uq$ command appends the single character whose 7-bit ASCII code is n to the text storage area of Q-register "q". @^Uq/string/ @:^Uq/string/ n@^Uq// n@:^Uq// Equivalent, respectively, to the ^Uqstring$, :^Uqstring$, n^Uq$, and n:^Uq$ commands, except that alternate delimiters are used and no characters are necessary. nUq Put n in the number storage area of Q-register q. m,nUq Equivalent to the nUqm command. That is, this command puts the number n into the numeric storage area of Q-register q and then returns the number m Standard TECO Page 5-32 Q-registers as a value. The command UAUB is useful at the beginning of a macro to save the two arguments specified on the macro call. (See the m,nMq command below.) n%q Add n to the contents of the number storage area of Q-register q. The resulting value contained in Q-register q is used as a numeric argument for the next command. If the next command does not require a numeric argument, this value is discarded. n%q$ Same as n%q but discards the value returned. %q Equivalent to 1%q. nXq Clear Q-register q and move n lines into it, where n is a signed integer. If n is positive, the n lines following the current pointer position are copied into the text storage area of Q-register q. If n is negative, the n lines preceding the pointer are copied. If n is zero, the contents of the buffer from the beginning of the line on which the pointer is located up to the pointer is copied. The pointer is not moved. The text is not deleted. Xq Equivalent to 1Xq. -Xq Equivalent to -1Xq. m,nXq Copy the contents of the buffer from the m+1th character through and including the nth character into the text storage area of Q-register q. M and n must be positive, and m should be less than n. .,.+nXq Copy the n characters immediately following the buffer pointer into the text storage area of Q-register q. N should be greater than zero. .-n,.Xq Copy the n characters immediately preceeding the buffer pointer into the text storage area of Q-register q. N should be greater than zero. n:Xq Append n lines to Q-register q, where n is a signed integer with the same functions as n in the nXq command above. The pointer is not moved. The colon construct for appending to a Q-register can be used with all forms of the X command. ]q Pop from the Q-register push-down list into Q-register q. Any previous contents of Q-register q are destroyed. Both the numeric and text parts Standard TECO Page 5-33 Q-registers of the Q-register are loaded by this command. The Q-register push-down list is a last-in first-out (LIFO) storage area. This command does not use numeric values. Numeric values are passed through this command as if it did not occur. This allows macros to restore Q-registers and still return numeric values. [Not in TECO-8] :]q Execute the ]q command and return a numeric value. A -1 indicates that there was another item on the Q-register push-down list to be popped. A 0 indicates that the Q-register push-down list was empty, so Q-register q was not modified. [Not in TECO-8] Table 5-9B lists the commands which permit data to be retrieved from the Q-registers. TABLE 5-9B: Q-REGISTER RETRIEVAL COMMANDS COMMAND FUNCTION Gq Copy the contents of the text storage area of Q-register q into the buffer at the current position of the buffer pointer, leaving the pointer positioned after the last character copied. :Gq Print the contents of the text storage area of Q-register q on the terminal. The text buffer and buffer pointer are not changed by this command. Qq Use the integer stored in the number storage area of Q-register q as the argument of the next command. :Qq Use the size of the text stored in the text area of Q-register q as the argument of the next command. nQq Return the ASCII value of the (n+1)th character in Q-register q. The argument n must be between 0 and the Q-register's size minus 1. If n is out of range, a value of -1 is returned. Characters within a Q-register are numbered the same way that characters in the text buffer are numbered. The initial character is at character position 0, the next character is at character position 1, etc. Therefore, if Q-register A contains "xyz", then 0QA will return the ASCII code for "x" and 1QA will return the ASCII code for "y". Standard TECO Page 5-34 Q-registers Mq Execute the contents of the text storage area of Q-register q as a command string. Mq commands may be nested recursively as far as TECO's push down storage will permit. nMq Execute the Mq command, using n as a numeric argument for the first command contained in Qregister q. m,nMq Execute the Mq command, using m,n as a numeric argument for the first command contained in Qregister q. [q Copy the contents of the numeric and text storage areas of Q-register q into the Q-register push-down list. This command does not alter either the numeric or text storage areas of Q-register q. It does not use numeric values. Numeric values are passed through this command as if it did not occur, allowing macros to save temporary Q-registers and still accept numeric values. The command sequence [A ]B copies the text and numeric value from Q-register A to Q-register B. [Not in TECO-8] Standard TECO Page 5-35 Arithmetic and Expressions 5.10 ARITHMETIC AND EXPRESSIONS The numeric argument of a TECO command may consist of a single integer, any of the characters listed in Table 5-11, the numeric contents of any Q-register, or an arithmetic combination of these elements. If an arithmetic expression is supplied as a numeric argument, TECO will evaluate the expression. All arithmetic expressions are evaluated from left to right without any operator precedence. Parentheses may be used to override the normal order of evaluation of an expression. If parentheses are used, all operations within the parentheses are performed, left to right, before operations outside the parentheses. Parentheses may be nested, in which case the innermost expression contained by parentheses will be evaluated first. Table 5-10A lists all of the arithmetic operators that may be used in arithmetic expressions. TABLE 5-10A: ARITHMETIC OPERATORS OPERATOR EXAMPLE FUNCTION + +2=2 Ignored if used before the first term in an expression. + 5+6=11 Addition, if used between terms. - -2=-2 Negation, if used before the first term in an expression. - 8-2=6 Subtraction, if used between terms * 8*2=16 Multiplication. Used between terms. / 8/3=2 Integer division with loss of the remainder. Used between terms. & 12&10=8 Bitwise logical AND of the binary representation of the two terms. Used between the terms. # 12#10=14 Bitwise logical OR of the binary of the two terms. Used between the terms. ^_ 5^_=-6 Unary one's complement. Used after an expression. This is a TECO command that complements its argument. Strictly speaking, it is not a unary operator. Standard TECO Page 5-36 Arithmetic and Expressions The following commands affect the radix in which TECO processes numeric strings, which may be either octal, decimal, or hexadecimal. All numeric strings typed in, typed out, or handled by the \ and n\ commands are interpreted in the current radix. [In TECO-10, the current radix is always decimal.] TABLE 5-10B: CONVERSION AND RADIX CONTROL COMMANDS COMMAND FUNCTION n= This command causes the value of n to be output at the terminal in decimal followed by a carriage return and line feed. Decimal numeric conversion is signed. For example, the unsigned number 65535 will output as -1 on TECO-11. TECO's radix is unaltered. n== This command causes the value of n to be output at the terminal in octal (base 8) followed by a carriage return and line feed. Octal numeric conversion is unsigned. For example, the unsigned number 8191 (decimal) will output as 17777 on TECO-8. TECO's radix is unaltered. n=== This command causes the value of n to be output at the terminal in hexadecimal (base 16) followed by a carriage return and line feed. Hexadecimal output is unsigned. TECO's radix is unaltered. [TECO-11 only] n:= n:== n:=== These commands are equivalent to n=, n==, and n===, except that they leave the carriage positioned at the end of the output. ^O (caret/O) causes all subsequent numeric input to be accepted as octal numbers. Numeric conversions using the \ or n\ commands will also be octal. The digits 8 and 9 become illegal as numeric characters. The octal radix will continue to be used until the next ^D command is executed or until TECO's radix is changed by an n^R command. NOTE: On TECO-10, this command only affects the immediately following digit string. ^D (caret/D) causes all subsequent numeric input to be accepted as decimal numbers. This is the initial setting. [Not in TECO-10] ^R This command returns the binary value of TECO's current radix. [TECO-11 only] Standard TECO Page 5-37 Arithmetic and Expressions n^R This command sets TECO's radix to the value of n. It is currently implemented only in TECO-11, where n may only be one of the values 8, 10, or 16 (representing octal mode, decimal mode, or hexadecimal mode). If n is not one of these values, TECO's radix remains unchanged and the ?IRA error message is produced. n\ The backslash command preceded by an argument inserts the value of n into the text buffer at the current position of the pointer, leaving the pointer positioned after the last digit of the insertion. The insertion is either signed decimal (decimal radix), unsigned octal (octal radix), or unsigned hexadecimal (hexadecimal radix). Note that \ is a "bidirectional" command. n\ inserts a string into text while \ (no argument) returns a numeric result. Standard TECO Page 5-38 Special Numeric Values 5.11 SPECIAL NUMERIC VALUES TECO maintains several internal variables which record conditions within TECO. The variable name is equivalent to the current contents of the variable and may be entered as a numeric argument to TECO commands. When the command is executed, the current value of the designated variable is substituted for the character and used in the numeric argument of the command. Some of the characters which stand for specific values associated with the text buffer have been introduced earlier in this manual. For example, the dot character (.), which represents the current pointer position, may be used in the argument of a T command. The command ".,.+5T" causes the 5 characters following the buffer pointer to be typed out. When this command is executed, the number of characters preceding the buffer pointer is substituted in each case for the "dot". The addition is then carried out, and the command is executed as though it were of the form "m,nT". Table 5-11 lists all of the characters which have special numeric values. Any of these characters may be used as numeric argument in place of the value it represents. Standard TECO Page 5-39 Special Numeric Values TABLE 5-11: CHARACTERS ASSOCIATED WITH NUMERIC QUANTITIES CHARACTER FUNCTION B Always equivalent to zero. Thus, B represents the position preceding the first character in the buffer. Z Equivalent to the number of characters currently contained in the buffer. Thus, Z represents the position following the last character in the buffer. . Equivalent to the number of characters between the beginning of the buffer and the current position of the pointer. Thus "." represents the current position of the pointer. H Equivalent to the numeric pair "B,Z", or "from the beginning of the buffer up to the end of the buffer." Thus, H represents the whole buffer. nA Equivalent to the ASCII code for the .+n+1th character in the buffer (that is, the character to the right of buffer pointer position .+n). The expression -1A is equivalent to the ASCII code of the character immediately preceding the pointer and 0A is equivalent to the ASCII code of the character immediately following the pointer (the current character). If the character position referenced lies outside the bounds of the text buffer, this command returns a -1. Mq The Mq command (execute the contents of the text storage area of Q-register "q" as a command string) may return a numeric value if the last command in the string returns a numeric value and is not followed by an ESCAPE. :Qq Equivalent to the number of characters in the text storage area of Q-register q. [Not in TECO-8] \ A backslash character which is not preceded by a numeric argument is equivalent to the value of the digit string (if any) beginning with the character immediately following the buffer pointer and ending at the next character that is not valid for the current radix. The first character may be a digit or + or -. As the backslash command is evaluated, TECO moves the buffer pointer to a position immediately following the digit string. If there is no digit string following the pointer, the backslash is equivalent to zero and the pointer position remains unchanged. Except on TECO-8, the digits 8 and 9 will stop the evaluation if TECO's current radix is octal. Standard TECO Page 5-40 Special Numeric Values ^B (caret/B) is equivalent to the current date via the following equations: OS/8: ^B = (((month*32)+day)*16)+((year-1970)&7)+k where k = 2048 if year>1977 and k=0 otherwise RT-11: ^B = (((month*32)+day)*32)+year-1972 RSTS/E: ^B = ((year-1970)*1000)+day within year RSX-11: ^B = ((year-1900)*16+month)*32+day VAX/VMS: ^B = ((year-1900)*16+month)*32+day TOPS-10: ^B = (((year-1964)*12+month-1)*31+day-1) ^E (caret/E) is equivalent to -1 if the buffer currently contains a full page of text (which was terminated by a form feed in the input file) or 0 if the buffer contains only part of a page of text (which either filled the buffer to capacity before the terminating form feed was read or which was not terminated by a form feed.) The ^E flag is tested by the P command and related operations to determine whether a form feed should be appended to the contents of the buffer on output. ^F (caret/F) is equivalent to the current value of the console switch register. n^F n is the terminal number plus 200000 (octal) for job n's terminal. -1^F is the terminal number plus 200000 (octal) for your job's terminal. The result is 0 if the specified job is detached or if there is no such job. [TECO-10 only] ^H (caret/H) is equivalent to the current time of day via the following equations: OS/8: ^H = 0 RT-11: ^H = 0 RSTS/E: ^H = minutes until midnight RSX-11: ^H = (seconds since midnight)/2 VAX/VMS: ^H = (seconds since midnight)/2 TOPS-10: ^H = 60ths of a second since midnight (or 50ths of a second where 50 Hz power is used) ^N (caret/N) is the end of file flag. It is equivalent to -1 if the file open on the currently selected input stream is at end of file, and zero otherwise. ^S (caret/S) is equivalent to the negative of the length of the last insert, string found, or string inserted with a "G" command, whichever occurred last. To back up the pointer to the start of the last insert, string found, etc., type "^SC". Standard TECO Page 5-41 Special Numeric Values [Not in TECO-8] ^T (caret/T) is equivalent to the ASCII code for the next character typed at the terminal. Every ^T command executed causes TECO to pause and accept one character typed at the terminal. See the ET flag description (section 5.16) for variations. ^Y (caret/Y) is equivalent to ".+^S,.", the n,m numeric argument spanning the text just searched for or inserted. This value may be used to recover from inserting a string in the wrong place. Type "^YXAFR$" to store the string in Q-register A and remove it from the buffer. You can then position the pointer to the right place and type "GA" to insert the string. [TECO-11 only] ^^x The combination of the Control-caret (double caret or double up-arrow) followed by any character is equivalent to the value of the ASCII code for that character. The "x" in this example may be any character that can be typed in to TECO. MODE CONTROL FLAGS The use of these flags is described below in section 5.16. ED Equivalent to the current value of the edit level flag. EH Equivalent to the current value of the help level flag. EO Equivalent to the version number of the version of TECO which is currently being run. This manual describes TECO-11 Version 35, TECO-8 version 7, and TECO-10 version 1. ES Equivalent to the current value of the search verification flag. [Not in TECO-8] ET Equivalent to the current value of the type out control flag. EU Equivalent to the current value of the upper lower case flag. EV Equivalent to the current value of the edit verify flag. [TECO-11 only] ^X (caret/X) is equivalent to the current value of the search mode flag. [Not in TECO-8] Standard TECO Page 5-42 Command Loops 5.12 COMMAND LOOPS You can cause a command string to be executed any number of times by placing the command string within angle brackets and preceding the brackets with a numeric argument designating the number of iterations. Iterated command strings are called command loops. Loops may be nested so that one command loop contains another command loop, which, in turn, contains other command loops, and so on. The maximum depth to which command loops may be nested is determined by the size of TECO's push-down list (system dependent), but is always greater than 10. The general form of the command loop is: n where "command string" is the sequence of commands to be iterated and n is the number of iterations. If n is not supplied then no limit is placed on the number of iterations. If n is 0 or less than 0 then the iteration is not executed at all; command control skips to the closing angle bracket. If n is greater than 0, then the iteration is performed n times. Search commands inside command loops are treated specially. If a search command which is not preceded by a colon modifier is executed within a command loop and the search fails, a warning message is printed [on TECO-11], the command loop is exited immediately and the command following the right angle bracket of the loop is the next command to be executed. If an unmodified search command in a command loop is immediately followed by a semicolon, it is treated as if it were a colon-modified search (see section 5.13). Standard TECO Page 5-43 Branching Commands 5.13 BRANCHING COMMANDS TECO provides an unconditional branch command and a set of conditional execution commands. To branch within a command string, you must be able to name locations inside the string. TECO permits location tags of the form: !tag! to be placed between any two commands in a command string. The name "tag" will be associated with this location when the command string is executed. Tags may contain any number of ASCII characters and any character except an exclamation mark. (When using the @ form of this command, any character except the delimiter is legal.) Since tags are ignored by TECO except when a branch command references the tagged location, they may also be used as comments within complicated command strings. The unconditional branch command is the O command which has the form: Otag$ where "tag" is a location named elsewhere in the command string and "$" signifies an ESCAPE. When an O command is executed, the next command to be executed will be the one that follows the tag referenced by the O command. Command execution continues normally from this point. Use of the O command is subject to two restrictions. First, if an O command is stored in a Q-register as part of a command string which is to be executed by an M command, the tag referenced by the O command must reside in the same Q-register. Second, an O command which is inside a command loop may not branch to a tagged location preceding the command loop. However, it is always possible to branch out of a command loop to a location which follows the command loop and then branch to the desired tag. The string argument in the O command has the same format as the string arguments in the search and E commands. String build characters such as ^EQq can be embedded within the string in TECO-11. Also, in TECO-11 and TECO-10,the O command may be @-sign modified. In that case, the syntax of the command would be @O/tag/ where / represents any delimiting character that does not appear within the tag. Branching into a conditional poses no problems, but branching into a command loop will causes unpredictable results. Although tags may contain any sequence of ASCII characters, good programming practice dictates that tags should not contain unusual characters (such as space, comma, ESCAPE, etc.) and that Standard TECO Page 5-44 Branching Commands they should be mnemonic for the piece of code to which they refer. There are many other branching commands. Most of these are considerably faster than the O command and should be used wherever convenient. They are all described in the table below. TABLE 5-10: Branching Commands Otag$ This command causes TECO to branch to the first occurrence of the specified label (tag) in the current macro level. In TECO-8 and TECO-11, branching to the left of the start of the current iteration is not permitted, and this command will only look for an occurrence of the specified tag following the < of the current iteration, if you are in an iteration. In any case, branching out of an iteration is poor programming practice. Command execution resumes at the first character after the delimiter terminating the specified tag. Using this syntax, any character except is permitted in the tag specification. The usual string build characters are permitted when specifying the tag. @O/tag/ Equivalent to Otag$ except that a delimiter (shown here as /) is used before and after the specified tag. Any character other than that delimiter is permitted inside the tag. The usual string build characters are permitted when specifying the tag. [Not in TECO-8] nOtag0,tag1,tag2,...$ This command causes TECO to branch to the tag specified by the nth tag in the accompanying list. The string argument to this command consists of a sequence of tags separated by commas. The tags may contain any characters other than comma or , however good programming practice dictates that the tags should consist only of letters and digits. There must be no intervening spaces since these would be considered part of the tag. If n is out of range, then command execution continues with the first command following the that delimits this command. [TECO-11 only] n@O/tag0,tag1,tag2,.../ Same as the preceding command except that the list of tags is bracketed by a delimiter shown here as "/". The delimiter can be any character that does not appear within the list of tags. In particular, using comma for the delimiter would not be very useful. [TECO-11 only] ; This command causes TECO to branch out of the current iteration, if the immediately preceding search (or Standard TECO Page 5-45 Branching Commands search and replace) command failed. In that case, control resumes at the character following the matching > at the end of the current iteration. On the other hand, if the preceding search succeeded, command execution continues with the character following the ;. If this command is encountered from outside of an iteration (in the current macro level), then the ?SNI error message is issued. n; This command causes TECO to branch out of the current iteration if the value of n is greater than or equal to 0. In that case, command execution resumes at the character following the matching > at the end of the current iteration. On the other hand, if n is less than 0, command execution continues with the character following the ;. If this command is encountered from outside of an iteration (in the current macro level), thent he ?SNI error message is issued. :; This command causes TECO to branch out of the current iteration if the immediately preceding search (or search and replace) command succeeded. In that case, control resumes at the character following the matching > at the end of the current iteration. On the other hand, if the preceding search failed, command execution continues with the character following the ;. If this command is encountered from outside of an iteration (in the current macro level), then the ?SNI error message is issued. [TECO-11 only] n:; This command causes TECO to branch out of the current iteration if the value of n is less than 0. In that case, command execution resumes at the character following the matching > at the end of the current iteration. On the other hand, if n is greater than or equal to 0, command execution continues with the character following the ;. If this command is encountered from outside of an iteration (in the current macro level), thent he ?SNI error message is issued. [TECO-11 only] ' This "command" is actually part of the syntax of TECO conditionals. It has no affect if "executed" other than to signify termination of the current conditional level. If an argument is specified to this command, the result is not defined. (Arguments pass through this command on TECO-11.) | This "command" is actually part of the syntax of TECO conditionals. If executed, it causes control to branch to the end of the conditional. Command execution resumes with the character following the ' that ends Standard TECO Page 5-46 Branching Commands the current conditional with the ELSE clause being skipped. > This "command" is actually part of the syntax of TECO iterations. If executed, it causes TECO to bump the current iteration count by 1 and test to see if the resulting count is equal to the maximum count permitted for the iteration (specified as an argument before the matching <). If the iteration count has not expired, then control returns to the command following the < at the beginning of the current iteration. If the iteration has expired, then command execution continues with the character following this >. If this command is encountered outside of an iteration (within the current macro level), then the ?BNI error message (or its equivalent) is issued. F> This command causes TECO to branch (flow) to the end of the current iteration. TECO effectively resumes execution at the matching >. The iteration count is tested as usual. If it has not expired, control returns back to the start of the iteration with the count having been incremented by 1. If the count was up, the iteration is exited and control continues with the first command after the >. If this command is encountered outside of an iteration, it has the same effect as the command. [TECO-11 only] F< This command causes TECO to branch (flow) to the start of the current iteration. TECO effectively resumes execution at the first command following the < at the beginning of the current iteration. The iteration count is not affected. If this command is issued outside of an iteration, it causes TECO to branch back to the start of the current command string (in the current macro level). [TECO-11 only] F' This command causes TECO to branch (flow) to the end of the current conditional. TECO effectively resumes execution at the first command following the ' at the end of the current conditional. Numeric arguments are eaten up by this command. If this command is issued while not in a conditional, the ?MAP error (or its equivalent) is issued. [TECO-11 only] F| This command causes TECO to branch (flow) to the else clause of the current conditional. TECO effectively resumes execution at the first command following the | at the end of the current THEN clause. If the current conditional has no ELSE clause, or if an unmatched ' is encountered before an unmatched |, then control resumes Standard TECO Page 5-47 Branching Commands at the command following the ' . Numeric arguments are eaten up by this command. If this command is issued while not in a conditional, the ?MAP error (or its equivalent) is issued. Well-structured programs should not need to use this command. [TECO-11 only] $$ The command causes TECO to exit from the current macro level. If this command is issued from top level (not from within a macro), then the command string execution is terminated and TECO returns to prompt level. Note that the second must be a true ESCAPE and may not be a ^[. Also, note that both ESCAPEs must be true TECO commands and not part of the syntax of some previous command. That is, the first does not count if it is the delimiting ESCAPE of a string. n$$ This command causes TECO to exit from the current amcro level, returning the number n as a value. This value will be used as the numeric argument to the first command following the macro call. m,n$$ This command causes TECO to exit from the current macro level, returning the pair of values m and n as arguments to the first command following the macro call. Good programming practice dictates that all ways of exiting a macro return the same number of arguments. ^C The (Caret-C) command when executed as a TECO command, causes command execution to stop and control return to TECO's prompt. No clean-up of push-down lists, flag settings, etc. is done. This command lets a macro abort TECO's command execution. [On TECO-8 and TECO-10, this command causes control to return to the operating system.] Consult the appendices for specific details concerning your operating system. ^C This command causes TECO to unconditionally abort and control exits from TECO. Control returns to the operating system. The second must be a true and may not be a Caret-C. Standard TECO Page 5-48 Conditional Execution Commands 5.14 CONDITIONAL EXECUTION COMMANDS All conditonal execution commands are of the form: n"X command-string ' or n"X then-command-string | else-command-string ' In the first form of the command, "n" is a numeric argument on which the decision is based, "X" is any of the conditional execution commands listed in table 5-14, and "command string" is the command string which will be executed if the condition is satisfied. The numeric argument is separated from the conditional execution command by a double quote (") and the command string is terminated with an apostrophe ('). If the condition is not satisfied, the command string will not be executed; execution will continue with the first command after the apostrophe. In the second form of the command, two command strings are specified. The first one is executed if the condition is satisfied and the second is executed if the condition is not satisfied. Only one of the command strings will be executed. After execution of the appropriate command string, control will continue with the first command after the apostrophe (unless the command string caused a branch out of the conditional to occur), since execution of the vertical bar command (|) causes TECO to scan to the next matching apostrophe. Conditional commands are similar to the IF-THEN-ELSE constructs that you find in other structured programming languages, although none can match the brevity and elegance of TECO's implementation. Nonetheless, you must use these facilities wisely. Good programming practice dictates that a branch into the range of a conditional (from outside that range) should not occur. Conditional execution commands may be nested in the same manner as iteration commands. That is, the command string which is to be executed if the condition on n is met may contain conditional execution commands, which may, in turn, contain further conditional execution commands. TABLE 5-14: CONDITIONAL EXECUTION COMMANDS COMMAND FUNCTION n"A Execute the following command string if n equals the ASCII code for an alphabetic character (upper or lower case A to Z). n"C Execute the following command string if n is the ASCII code of any character that is a symbol constituent. Standard TECO Page 5-49 Conditional Execution Commands This is usually one of the upper or lower case letters A to Z, one of the digits 0 to 9, or period, or dollar sign, but may include additional characters on some operating systems. Consult the appropriate appendix. n"D Execute the following command string if n equals the ASCII code for a digit (0 to 9). n"E Execute the following command string if n is equal to zero. n"F Execute the following command string if n is FALSE. Equivalent to n"E. n"G Execute the following command string if n is greater than zero. n"L Execute the following command string if n is less than zero. n"N Execute the following command string if n is not equal to zero. n"R Execute the following command string if n equals the ASCII code for an alphanumeric (upper or lower case A to Z or 0 to 9). n"S Execute the following command string if n is SUCCESSFUL. Equivalent to n"L. n"T Execute the following command string if n is TRUE. Equivalent to n"L. n"U Execute the following command string if n is UNSUCCESSFUL. Equivalent to n"E. n"V Execute the following command string if n equals the ASCII code for a lower case alphabetic character (lower case A to Z). [Not in TECO-8] n"W Execute the following command string if n equals the ASCII code for an upper case alphabetic character (upper case A to Z). [Not in TECO-8] n"< Identical to n"L n"> Identical to n"G n"= Identical to n"E Standard TECO Page 5-50 Retrieving Environment Characteristics 5.15 RETRIEVING ENVIRONMENT CHARACTERISTICS The following TECO commands return values of interest to users who want information about their current job, the operating system, their terminal, etc. TABLE 5-15A: RETREIVING ENVIRONMENT CHARACTERISTICS COMMAND FUNCTION -1EJ Return a number representing the computer and operating system upon which TECO is currently running. This value has the form 256m+n where m is a number representing the computer in use and n is a number representing the operating system that is running. Current values of m and n are: Computer (m) Operating System (n) 0 PDP-11 0 RSX-11D 1 RSX-11M 2 RSX-11S 3 IAS 4 RSTS/E 5 VAX/VMS (compatibility mode) 6 RT-11 1 PDP-8 0 OS/8 2 PDP-10 0 TOPS-10 3 PDP-20 0 TOPS-20 4 VAX-11 0 VAX/VMS (native mode) 0EJ Returns a value equal to your job number. On single-user systems, this is always a 0. 1EJ Returns a value equal to your console keyboard number (the keyboard you detached from if you are running detached). On single-terminal systems, this is always a 0. 2EJ Returns a value equal to your operating system's user identification number. This may be called your UIC, PPN, Group, etc. under various operating systems. Consult the appendices for more information. TABLE 5-15B: SETTING ENVIRONMENT INFORMATION n,1EJ Set the terminal number to receive output. This will not affect terminal input. Your job will remain attached to, or detached from, your terminal, whichever it was before. Output will only occur if the specified Standard TECO Page 5-51 Retrieving Environment Characteristics terminal is ASSIGNed with a monitor ASSIGN command (you may ^C, issue that command and continue) and if your job has POKE privileges. This command also sets the terminal to be reattached if the set detach flag (64&ET) is cleared. The reattaching operation requires [1,2] or JACCT privileges. [TECO-10 only] n,2EJ Sets your [p,pn] to n where n has the same format as the number returned by the 2EJ command. Issuance of this command requires the appropriate privileges. [TECO-10 only] Standard TECO Page 5-52 Mode Control Flags 5.16 MODE CONTROL FLAGS TECO has flags which control various aspects of its operation. These flags, referenced with the commands "ED", "EH", "EO", "ES", "ET", "EU", "EV", and "^X", are called the ED, EH, EO, ES, ET, EU, EV, and X flags, respectively. You can find a flag's current setting by executing its command name without an argument; the current setting of the flag is returned as a value. A flag may be set to a specific value by executing its command name preceded by a numerical argument; the flag is set to the value of the argument. The following table describes the commands that set and clear flags; represents any of the flags listed above. TABLE 5-16A: FLAG MANIPULATION COMMANDS Return value of flag. n Set value of flag to n. m,n In the flag, turn off those bits specified by m and turn on those bits specified by n. [Not in TECO-8] 0,n Turn on the bits in the flag specified by n. [Not in TECO-8] m,0 Turn off the bits in the flag specified by m. [Not in TECO-8] The flags have the following functions: TABLE 5-16B: MODE CONTROL FLAGS COMMAND FUNCTION ED The edit level flag, a bit-encoded word that controls TECO's behavior in various respects. Any combination of the individual bits may be set as the user sees fit. The bits have the following functions: ED&1 Allow caret (^) in search strings. If this bit is reset (off), a caret (^) in a search string modifies the immediately following character to become a control character. When this bit is set, a caret in a search string is simply the literal character caret. If you are editing a file that contains many caret characters (e.g., a RUNOFF file with case control), you will want to set this bit. Standard TECO Page 5-53 Mode Control Flags ED&2 Allow all Y and _ commands. If this bit is set, the Y (Yank) command and _ (underscore or backarrow) command work unconditionally as described earlier in the manual. If reset (off), the behavior of the Y and _ commands are modified as follows: If an output file is open and text exists in the text buffer, the Y or _ command will produce an error message and the command will be aborted leaving the text buffer unchanged. Note that if no output file is open the Y and _ commands act normally. Furthermore, if the text buffer is empty the Y command can be used to bring in a page of text whether or not an output file is open (HKY will always work). The _ command will succeed in bringing one page of text into an empty text buffer but will fail to bring in successive pages if an output file is open. ED&4 When this bit is not set (0), TECO will try to expand memory as much as it can in order to try to fit entire pages into memory when requested to do so. If this bit is set (1), arbitrary memory expansion will not occur. In that case, TECO will expand memory if only necessary on the A command and not on the Y, P, or N commands. This bit is always set in TECO-10 and has no significance in TECO-8 or in TECO-11 on RT-11. ED&8 Reserved for future use. ED&16 Allow failing searches to preserve dot. If this bit is set (1), then whenever a search fails, the original location of the text buffer pointer will be preserved. If this bit is off (0), then failing searches (other than bounded searches) leave the text buffer pointer at pointer position 0 after they fail. The initial value of ED&1 is system dependent (See appendices). The initial value of the other bits in the ED flag is 0. EH The help level flag, which controls the printing of error messages and failed commands. EH&3 The low two bits of EH (value range 0 through 3) control the printing of TECO error messages as follows (assuming the low two bits have value m): If m is equal to 1, error messages are output in Standard TECO Page 5-54 Mode Control Flags abbreviated form ("?XXX"). If m is equal to 2, error messages are output in normal form ("?XXX Message"). If m is equal to 3, error messages are output in long or "War and Peace" form, that is, a paragraph of informative material is typed following the normal form of the error message. This mode is not implemented in TECO-11, in which case m=3 is equivalent to m=2. EH&4 If this bit of EH is set, the failing command is also output up to and including the failing character in the command followed by a question mark. (Just like TECO's response to the typing of a question mark immediately after an error.) This bit is not supported by TECO-10. The initial value is 0 which is equivalent to a value of 2. EO Setting the value of the EO flag to n allows features that were peculiar to that version of TECO to work. [TECO-10 only] ES The search verification flag, which controls the text typed out after searches. If n is equal to 0, nothing is typed out after searches. If n is -1, the current line is typed out when a successful search at top level is completed (i.e., a V command is done automatically). If n is between 1 and 31, the current line is typed out with a line feed immediately following the position of the pointer to identify its position. If n is between 32 and 126, the current line is typed out with the ASCII character corresponding to the value of n immediately following the position of the pointer to identify its position. If you want to see more than one line of type out, use the form m*256+n. The n is the same as above. The m is the number of lines of view. For example, 3*256+^^! would be two lines on either side of the found line, and the found line with the character "!" at the pointer's position. The ES flag does not apply to searches executed inside iterations or macros; lines found inside iterations or macros are never typed out. [Not in TECO-8] The initial value of ES is 0. ET The ET flag is a bit-encoded word controlling TECO's treatment of the console terminal. Any combination of the individual bits may be set. The bits have the following functions: ET&1 Type out in image mode. Setting this bit inhibits all of TECO's type out conversions. Standard TECO Page 5-55 Mode Control Flags All characters are output to the terminal exactly as they appear in the buffer or ^A command. For example, the changing of control characters into the "caret/character" form, and the conversion of to $ (dollar sign) are suppressed. This mode is useful for driving displays. It should be used with caution, especially if you are talking to TECO over a dial-up line. ET&2 Process DELETEs and s in "scope" mode. Scope mode processing uses the cursor control features of CRT type terminals to handle character deletion by actually erasing characters from the screen. ET&4 Read lower case. TECO normally converts all lower case alphabetics to upper case on input. Setting this bit causes lower case alphabetics to be input as lower case. TECO commands and file specifiers may be typed in either upper or lower case. For the purpose of searches, however, upper and lower case may be treated as different characters. (See ^X flag). ET&8 Read without echo for ^T commands. This allows data to be read by the ^T command without having the characters echo at the terminal. Normal command input to TECO will echo. ET&16 Cancel on type out. Setting this bit will cancel any outstanding when the next type out occurs. After TECO has canceled the , it will automatically reset the bit. ET&32 Read with no wait. This enables the ^T command to test if a character is available at the user terminal. If a character has been typed, ^T returns the value of the character as always. If no character has been typed, ^T immediately returns a value of -1 and execution continues without waiting for a character. ET&64 Detach flag (See appendices). ET&128 When this bit is set: 1) all informational messages are supressed, 2) any causes the immediate termination of TECO, and 3) any error causes the termination of TECO after the error message is printed. Standard TECO Page 5-56 Mode Control Flags ET&256 If this bit is set, all lines output to the terminal are truncated to the terminal's width if needed. (RSTS/E, RSX-11, and VAX/VMS only.) ET&512 If this bit is set, the scope "WATCH" feature of TECO is present and your terminal is a scope type terminal. This bit is a read-only bit; its state cannot be altered. (See Section 5.17.) ET&1024 If this bit is set, the refresh scope "WATCH" feature of TECO is present and a refresh scope is available. This bit is a read-only bit; its state cannot be altered. (See Section 5.17.) ET&32768 If this bit is set and a is typed, the bit is turned off, but execution of the current command string is allowed to continue. This allows a TECO macro to detect typed s. In TECO-8, this bit is the 2048's bit rather than the 32768's bit. The initial setting of ET is operating system dependent (See appendices). In addition, some of the ET bits are automatically turned off by certain error conditions. EU The upper/lower case flag. If n is -1, no case flagging of any type is performed on type out, lower case characters are output as lower case characters. If n is 0, lower case characters are flagged by outputting a ' (quote) before the lower case character and the lower case character is output in upper case; upper case characters are unchanged. If n is +1, upper case characters are flagged by outputting a ' (quote) before each one and then the upper case character is output; lower case characters are output as their upper case equivalents. The initial value of the EU flag is -1 if TECO can tell from the operating system that the user's terminal supports display of lower case characters; otherwise te initial value is 0. Consult the appendices for more details. EV The edit verify flag is decoded just like the ES flag. Just before TECO prints its prompting *, the EV flag is checked. If it is non-zero the lines to be viewed are printed on the terminal. The initial value of the EV flag is 0. [TECO-11 only] Standard TECO Page 5-57 Mode Control Flags ^X The search mode flag. [Not in TECO-8] If n is 0, the text argument in a search command will match text in the text buffer independent of case in either the search argument or the text buffer. Thus the lower case alphabetics match the upper case alphabetics and "`", "{", "|", "}", "~" match "@", "[", "\", "]", "^" respectively. If n is -1, the search will succeed only if the text argument is identical to text in the text buffer. The initial value of the ^X flag is 0. Standard TECO Page 5-58 Scope Commands 5.17 SCOPE COMMANDS The W command (scope "WATCH") is present in most implementations of TECO. There are two different variations of the W command. Neither, one, or both may be present. ET flag Bits 9 and 10 indicate which variation(s) are configured and can be used. 5.17.1 Video Terminal scope "WATCH" If the VT support is present and your terminal is a video terminal (such as a VT05, VT52, or VT100), ET flag Bit 9 (value 512) will be on. TABLE 5-17A: VIDEO TERMINAL WATCH COMMANDS Command Function -1W Refresh the terminal's screen to show the contents of the text buffer. -nW Tell the video terminal screen refresher that the top n-1 lines of the screen have been altered. The screen refresher will completely redraw the top n-1 lines of the screen upon the next -1W command. nW Place the default cursor line at line n of the VT52's screen. The initial default cursor line is line 16. This command makes the window support forget the screen image and any special associated modes (SEEALL, MARK, HOLD). 0W Forget screen image, SEEALL mode, mark, hold mode, scrolling, and set cursor line to default (2/3 of the way down the screen) W Do scrolling update if scrolling; else nop. 32768W Forget that output was done. Normally, if the user outputs to the terminal with a command such as T, n^T, or ^A, TECO will believe that the window needs updating, and upon the next -1W command, TECO will refresh the entire window display. Issuing the 32768W command informs TECO that the output command did not destroy the window. [TECO-11 only] The :W command is used to interrogate and set video terminal status information, as well as implement some of the more advanced features of the video terminal "WATCH" functions. Standard TECO Page 5-59 Scope Commands TABLE 5-17B: VIDEO TERMINAL STATUS COMMANDS Command Function 0:W Return a number representing the type of scope in use as the editing terminal. Current values are: 0 VT52 1 VT61 [TECO-10 only] 2 VT100 in VT52 mode 4 VT100 in ANSI mode 6 VT05 :W Equivalent to 0:W 1:W Return the horizontal size of the user's editing scope. This number represents the number of character positions available horizontally along the face of the scope. 2:W Return the vertical size of the user's editing scope. This number represents the number of lines of text that can appear on the screen of the terminal. 3:W Returns SEEALL mode. 0 represents off and -1 represents on. In SEEALL mode, a visible indication is shown in the window for every character, including characters that normally don't print. 4:W Returns mark status of window support. 0 means that no mark has been set. A value of n means that a mark has been set at window position n-1. This status is used by software that uses the window support and by the support itself in the case of scopes that support reverse video. 5:W Returns the hold mode indicator. 0 means off, -1 means hold whole screen, and a positive value, n, means hold all but top and bottom n lines. If hold mode is on, then scrolling is inhibited until the cursor is about to run off either end of the screen. This makes the window display more palatable on terminals on a slow line. If hold mode is on, the window support will scroll the window as necessary in an attempt to keep the cursor centered. 6:W Returns buffer pointer position of character that was in the upper left hand corner of the window as of the last -1W command. 7:w Returns the number of scrolling lines. If n is Standard TECO Page 5-60 Scope Commands zero, then scrolling is turned off. Consult the appendices for details. -256+n:W inserts characters at "dot" until... characters are read (echo off) from the terminal and inserted at "dot" until and according to the microcoded bits in n 128 => return immediately if no characters 64 => return on any character 32 => don't update screen (i.e., don't do a -1W) 2 => return on TAB's 1 => no need to initially refresh the screen return is always done on control characters (0 through 37 and 177 except TAB) returned value has return character code in low byte (0 through 177 or 377 for returned immediately); sign bit (value 32768) is set if one or more inserts were done the screen is only updated if 32 is not in n and there is no typeahead to process; if 128 in n is not set then the update will occur after all typeahead insert(s) are done n,:W same as n,0:W n,0:W sets scope type (n must be 0, 2, 4, or 6) n,1:W sets scope width (n must be between 10 and 254 and even) n,2:W sets scope height (n must be between 10 and 127) n,3:W sets SEEALL mode (n=0 for off, n<>0 for on) n,4:W sets mark (n=0 for none, n<>0 for mark @ n-1) n,5:W sets hold mode (n=0 for off, n=-1 for hold whole screen, n>0 for hold all but top and bottom n lines) n,6:W sets position for upper left hand corner for next -1W (n=0 for default cursor positioning, n<>0 for upper left hand corner @ n-1) (applies only if hold mode is on and cursor is within the specified limits) n,7:W sets number of scrolling lines (n=0 for no scrolling, n<>0 for scroll bottom n lines, where n must be greater than 1 and scope height minus n must be greater then 9) same operation as -256+n:W except if m typeahead insert(s) are done the screen will be updated (provided 32 is not set in n) Standard TECO Page 5-61 Scope Commands Notes on Hold Screen mode (5:W) If "hold whole screen" mode (-1,5:W) is set, the hardware scrolling of the scope will never be used. This allows a program to set hold whole screen mode (-1,5:W) and, then, shorten the scope's height (n,2:W) without problems. The bottom 'unused' lines of the scope will never be altered by TECO and can be used by the program for other purposes. Notes on Scrolling (7:W) Whenever a scrolling lines modification is issued (n,7:W), TECO alters the scope's height (2:W) accordingly. For example, if 2:W is currently returning a value of 24, then, after a 5,7:W command, 2:W will return a value of 19. Doing a 0,7:W will restore 2:W to returning 24. 5.17.2 Refresh scope "WATCH" If refresh scope support is present and a refresh scope is available (such as a VS60 or a VR12), bit value 1024 of the ET flag will be on. TABLE 5-17C: REFRESH SCOPE WATCH COMMANDS Command Function W Update the refresh scope screen to reflect the contents of the text buffer surrounding the text pointer ("dot"). 0W Turn off the refresh scope display. nW Set the number of lines to be displayed around the text pointer to n. Standard TECO Page 5-62 Programming Aids 5.18 PROGRAMMING AIDS In addition to the command string editing capabilities described in Chapter 4, TECO includes various features to facilitate programming. These are described in the following sections. 5.18.1 Text Formatting The characters carriage return, line feed, vertical tab, and space are ignored in command strings, except when they appear as part of a text argument. Numeric values are not affected. (Inserting a space between digits within a digit string may cause unpredictable results). These characters may be inserted between any two TECO commands to lend clarity to a long command string. The carriage return/line feed combination is particularly useful for typing command strings which are too long to fit on a single line. If the character form feed is encountered in a command string and it is not part of a text argument, a form feed is output to the terminal. This can be used to format terminal output. On TECO-10, execution of the form feed command will clear the screen if TECO is in scope command string editing mode (2&ET on). 5.18.2 Comments One of the most powerful features of TECO is its ability to store very long command strings so that a given sequence of commands may be executed whenever needed. Long command strings may be thought of as editing programs and, like any other type of program, they should be documented by means of comments. Comments may be inserted between any two commands by using a tag construction of the form: !THIS IS A COMMENT! Comments may contain any number of characters and any characters except the special characters. Thus a long TECO macro might look like: TECO commands !This comment describes line 1! TECO commands !This comment describes line 2! more commands more commands !end of comment string! Do not use characters to format long command strings! Only , , and can be used to format command strings since is an insertion command. Standard TECO Page 5-63 Programming Aids Good TECO code is well structured and adequately commented. Unfortunately, massive comments in a TECO macro tend to slow execution, especially if they appear within text scanned by GOTOs or unsatisfied conditionals. Unless speed is not a goal, it is common practice in larger TECO programs to strip out comments before loading up TECO macros. Thus the TECO program can be adequately commented, yet still run efficiently. A large TECO program can start by placing a comment stripper in a Q-register, say Q-register C. Then it can successively put subroutines (macro text) into the text buffer, do an MC, and load the appropriate Q-register with the resulting text buffer, until all the subroutines have been loaded. Finally, Q-register C can be zeroed and the program started. In order for you to strip the comments without losing essential tags, you must make a convention for the format of your comments so that your comment stripper can distinguish them from tags. There are two common conventions. In one, the first character in every comment after the initial ! is some distinctive character, such as *. In the other, all tags start in the left margin and all comments are embedded within the text. Any large comment that wants to be on a line by itself starts with a before the !. Both methods allow for readable code and easy comment stripping. 5.18.3 Messages The command may be used to print out a statement at any point during the execution of a command string. The command has the general form: ^Atext or @^A/text/ The first ^A is the actual command, which may be entered by striking the control key and the A key simultaneously or by typing a caret (uparrow) followed by an A character. The second character of the first form shown is the command terminator, which must be entered by typing the control key and the A key simultaneously. In the second form, the second occurence of the delimiting character (shown as slash in the example) terminates the message. Upon execution, this command causes TECO to print the specified message at the terminal. The ^Amessage command is particularly useful when it precedes a command whose numeric argument contains ^T or ^F characters. The message may contain instructions notifying the user as to what sort of input is required. Standard TECO Page 5-64 Programming Aids 5.18.4 Tracing A question mark entered betweeen any two commands in a command string causes TECO to print all subsequent commands at the terminal as they are executed. Commands will be printed as they are executed until another question mark character is encountered or the command string terminates. Standard TECO Page 5-65 Programming Aids 5.18.5 Convenience Characters In addition to the characters mentioned in Section 5.18.1, there are several characters which have no special meaning to TECO but which may be used to help format your TECO programs and command strings. Judicious use of these commands will make your program easier to read and maintain. These characters are described in the table below: CHARACTER MEANING A null (ASCII 0) encountered as a TECO command will be ignored. Numeric values are not affected. A null read in from an input file will be discarded (except under RSX-11 and VAX/VMS). A null typed in from a terminal will be ignored. An ESCAPE that is executed as a TECO command (as distinct from an ESCAPE that is part of the syntax of some other TECO command) is ignored by TECO; however any pending numeric values are discarded. This command is useful for discarding the value returned from a command (such as n%q) when that value is not needed. ^[ Same as . Like any other TECO command that is a control character, it may be entered in up-arrow mode. In that mode, ^[ is useful on systems whose line-printer spoolers do not visibly print the ESCAPE character. On some older terminals, there is no ESCAPE key. Instead, there may be a key labelled ALTMODE or PREFIX which sends TECO a character whose ASCII value is 175 or 176. In such a case, TECO will treat these characters as if they were typed in as an ESCAPE (Octal 33), provided lower to upper case conversion is enabled. $ (dollar sign) Same as . [TECO-10 only] Note that and
are valid TECO commands and must not be used as aids to formatting TECO programs. 5.18.6 Memory expansion The nEC command can be used to make TECO reclaim lost space after it had expanded memory usage. nEC tells TECO to expand or contract until it uses nK words of memory. If this is not Standard TECO Page 5-66 Programming Aids possible, then TECO's memory usage does not change. The 0EC command tells TECO to shrink back to its original size (use the least amount of memory possible). [TECO-10 only] 5.18.7 Case Control The and TECO commands are used to specify automatic case control for alphabetic characters typed into strings. CHARACTER MEANING ^V puts TECO into lower case conversion mode. In this mode, all alphabetic characters in string arguments are automatically changed to lower case. This mode can be overridden by explicit case control within the search string. This command makes all strings behave as if they began with a ^V^V. [TECO-10 only] ^W puts TECO into upper case conversion mode. In this mode, all alphabetic characters in string arguments are automatically changed to upper case. This mode can be overriden by explicit case control within the search string. This command makes all strings behave as if they began with ^W^W. [TECO-10 only] 0^V Returns TECO to its original mode. No special case conversion occurs within strings except those case conversions that are explicitly specified by ^V and ^W string build constructs located within the string. [TECO-10 only] 0^W Same as ^V. [TECO-10 only] Standard TECO Page 5-67 5.19 MANIPULATING LARGE PAGES TECO is designed to operate most efficiently when editing files that contain no more than several thousand characters per page. (TECO storage includes Q-register storage and buffer space. The size of the text storage area is dynamic and depends on the amount of available memory.) If any page of an input file is too large to fit in the text area, the TECO input commands will terminate reading that page into memory when the first line feed is encountered after a point that the buffer is 3/4 full. (See appendices for details.) You can make room by positioning the pointer past a section of text at the beginning of the buffer and moving that section out of the buffer with the commands: 0,.PW0,.K It is sometimes advantageous to restrict the amount of the file that is present in the buffer. For example, each insert and delete command must move the entire text that is beyond the point of insertion or deletion. An operation that does many small inserts or deletes may therefore run extremely slowly if the text buffer is large. Such an operation can be sped up substantially by reading the input file with n:A commands and explicitly writing the processed text. Standard TECO Page 5-68 Techniques 5.20 TECHNIQUES AND EXAMPLES The most elementary TECO application, described in Chapter 1 of this manual, is creating and editing ASCII files on-line. The user enters short command strings, often consisting of a single command, and proceeds from task to task until the file is completely edited. Since every editing job is simply a long sequence of TECO commands, you may accomplish an entire job with one long command string made up of all the short command strings placed end to end with the intervening double ESCAPE characters removed. A long command string that performs a certain editing task can be considered a TECO "editing program". Editing programs may be written (using TECO) and stored in the same manner as any other ASCII file. Whenever the program is needed, it may be read into the buffer as text, stored in a Q-register, and executed by an Mq command. For more complex editing jobs, you may want to write and maintain a collection of specialized "editing subroutines." TECO subroutines can perform such elementary functions as replacing every occurrence of two or more consecutive spaces with a tabulation character, for example, or ensuring that words are not hyphenated across a page boundary. When an editing problem arises, you can load the right combination of subroutines into various Q-registers, augment them with additional commands if necessary, and call them by a "mainline" command string. Editing subroutines are essentially macros; that is, sequences of commands which perform commonly required editing functions. The most powerful application of TECO is the creation and use of a macro library. As you perform an editing job, look for sequences of operations which might be required in future editing assignments. Load all of the TECO commands required to perform such an operation into a Q-register. When the job is finished, write the contents of the Q-register onto an output file (via the buffer) and save it in the macro library. The nMq and m,nMq commands, which were designed to facilitate use of macros, permit run-time numeric arguments to be passed to a macro. TECO macros can preserve the user's radix, flag values, etc. By using the Q-register push-down list, the macro can save and then restore values and/or text. For example: [0 [1 [2 ! Save contents of Q-registers 0, 1 and 2 ! +0U0 ! Put any calling argument into Q-register 0 ! 10U1 ! Put a 10 (if radix is decimal) or 8 (if radix is octal) into Q-reg 1 ! ^D ! Ensure that the current radix is now decimal ! EUU2 ! Save the case flagging flag ! -1EU ! Ensure no case flagging ! Q0"E 3U0 ' ! Default calling argument to 3 ! Standard TECO Page 5-69 Techniques ... Q2EU ! Restore the case flagging flag ! 10-Q1"N ^O ' ! Restore radix as octal if needed ! ]2 ]1 ]0 ! Restore contents of Q-registers 2, 1, and 0 ! The EI command is particularly useful for executing macros from a library, since with it they may be read without disturbing the current input file. This makes it unnecessary to plan in advance which macros might be needed; it also saves Q-register storage space. You can retrieve two kinds of TECO command files with an EI command: a file containing a TECO command that loads the macro into a Q-register for later use, or a file containing just the macro (which must be retrieved with EI each time it is used). The following examples are intended to illustrate some of the techniques discussed above. It would not be practical to include examples of the use of every TECO command, since most of the commands apply to many diverse situations. Instead, you are encouraged to experiment with the individual commands on scratch files. EXAMPLE 1: SPLITTING, MERGING, AND REARRANGING FILES Assume that there is a file named PROGRAM.DAT on the system disk and that this file contains data in the following form: AB CD EF GH IJ KL MN OP where each of the letters A, B, C etc., represents 20 lines of text and represents a form feed character. The user intends to rearrange the file so that it appears in the following format: AOB D MN EF ICJ KL P GH The following sequence of commands will achieve this rearrangement. (Search command arguments are not listed explicitly.) Call TECO. *2ED$$ Allow all Y commands. *EBPROG.DAT$Y$$ Specify input file and get first page. *NC$$ Search for a character string in C, writing A and B on the output file. *J20X1$$ Save all of C in Q-register 1. *20K$$ Delete C from the buffer. *NG$$ Search for a character string in G, writing D, E, and F on the output file. *HX2$$ Save G and H in Q-register 2. *Y$$ Delete GH from the buffer and read IJ. *20L$$ Move the pointer to the beginning of J. *G1$$ Insert C, which was stored in Q-register 1. Standard TECO Page 5-70 Techniques *NM$$ Search for a character string in M, writing ICJ and KL on the output file. *HX1$$ Save MN in Q-register 1 (the previous contents is overwritten). *Y$$ Delete MN and read OP *J20X3$$ Save all of O in Q-register 3. *20K$$ Delete O from the buffer. *P$$ Write P onto the output file, leaving the buffer cleared (the input file is exhausted). *G2$$ Bring GH into the buffer from Q-register 2. *HPEF$$ Write GH on the output file and close it. *EBPROG.DAT$Y$$ Open the partially revised file. *20L$$ Move the pointer to the beginning of B. *G3$$ Insert all of O from Q-register 3. *ND$$ Search for a character string in D writing AOB on the output file. *PWHK$$ Write D on the output file and clear buffer. *G1$$ Bring all of MN from Q-register 1 into the buffer. *EX$$ Write MN onto the output file, then close the file and exit. At this point the file has been rearranged in the desired format. Of course, this rearrangement could have been accomplished in fewer steps if the commands listed above had been combined into longer command strings. Note that the asterisks shown at the left margin in this example are generated by TECO, and not typed by the user. Assume, now, that the same input file, containing data in the form: AB CD EF ... OP is to be split into two separate files, with the first file containing AB CD and the second file containing KL M, while the rest of the data is to be discarded. The following commands could be used to achieve this rearrangement: Call TECO. *2ED$$ Allow all Y commands. *ERFILE$EWFILE1$$ Open the input file and the first output file. *Y$$ Read AB into the buffer. *P$$ Write AB onto the output file and read CD into the buffer. *HPEF$$ Write CD onto the output file (without appending a form feed), and close the first output file. *_K$$ Search for a character string in K. After this command has been executed, the buffer will contain KL. No output is generated. *EWFILE2$P$$ Open the second output file and write KL onto Standard TECO Page 5-71 Techniques it. Read MN into the buffer. *20L0,.P$$ Move the pointer to the end of M, then write M onto the output file. *EX$$ Close the output file and exit. As a final example of file manipulation techniques, assume that there are two files. One file is MATH.ONE, which contains information in the form: AB CD EF GH IJ KL and the other is MATH.TWO, which contains: MN OP QR If both of these files are stored on DK1, the following sequence of commands may be used to merge the two files into a single file, MATH.NEW, which contains all of MATH.TWO followed by the latter half of file MATH.ONE in the following format: MN OP QR GH IJ KL Call TECO. *2ED$$ Allow all Y commands. *ERDK1:MATH.TWO$$ Open the first input file. *EWMATH.NEW$$ Open the output file on the default device. *Y$$ Read MN into the text buffer. *NR$$ Search for a character string in R, writing MN and OP onto the output file. *PW$$ Write QR onto the output file, appending a form feed. *ERDK1:MATH.ONE$$ Open the second input file. *HKY$$ Read AB into the buffer. QR is over-written. *_G$$ Search for a character string in G, deleting AB, CD, and EF, leaving GH in the buffer. *NK$$ Search for a character string in K, writing GH and IJ on the output file, leaving KL in the buffer. *HPEX$$ Write KL onto the output file (without appending a form feed) and close the file, then exit. EXAMPLE 2: ALPHABETIZING BY BINARY SEARCH Assume that TECO is running and that the buffer contains many short lines of text beginning with an alphabetic character at the left margin (i.e., immediately following a line feed). The lines might consist of names in a roster, for example, or entries in an index. The following command string will rearrange the lines into rough alphabetical order, grouping all lines which begin with the character "A" at the beginning of the page, followed by all lines with "B", and so on. Note that the Standard TECO Page 5-72 Techniques algorithm could be extended to place the entries in strict alphabetical order by having it loop back to perform the same binary sorting operation on successive characters in each line. !START! J 0AUA !Load first character of first line into Q-register A ! !CONT! L 0AUB !Load first character of next line into Q-register B ! QA-QB"G XA K -L GA 1UZ ' !If A>B, switch the lines and set a flag (Q-register Z) ! QBUA !Load B into A ! L Z-."G -L @O/CONT/ ' !Loop back if there is another line in the buffer ! QZ"G 0UZ @O/START/ ' !Repeat if a switch was made on the last pass ! The same algorithm can be coded in a more structured way as follows: 0UZ !clear repeat flag! B, switch the lines and set a flag ! QBUA !Load B into A ! L .-Z;> !Loop back if there is another line in the buffer ! QZ;> !Repeat if a switch was made on the last pass ! This example is a bit shorter and does not use any GOTOs. It will also run somewhat faster. Standard TECO PAGE 6-1 Alphabetical List of Commands CHAPTER VI ALPHABETICAL STANDARD COMMAND SUMMARY This chapter presents all the TECO commands in alphabetical order, with a description of the use of each and, in most cases, an example of how it might be used in practise. Only TECO commands are given. Immediate action commands and other special commands are not given. Special characters in strings are also not included in this chapter. The 'Alphabetical Order' used is as follows:- 1. Indexed by 'major character' of command in the order, letters in alphabetical order followed by special characters in collating sequence order. 2. For each major character the first entry is for the command that uses that character only, possibly modified by a special character (e.g. A, :A ...). 3. For each major character the next entry is for the command that uses that character preceded by a number, if different to that above (e.g. nA). 4. For each major character the next entry is for the command that uses the control-character form of that character, if different to that above (e.g. ^A). 5. For each major character the next entries are for any commands that use that character followed by other minor characters, arranged in order (as above) of minor characters (e.g. FB, F|). 6. Commands such as are entered as if they were TAB. Standard TECO PAGE 6-2 A (append) A APPEND COMMAND ================================================================= Append next page to end of buffer. FORMAT: A :A n:A (Note that nA is a completely different command) ================================================================= The A (append) command reads in the next page of the input file without clearing the current contents of the editing buffer. TECO concatenates this information to that which is already in the buffer, i.e., TECO places it in the buffer following buffer position Z. An A command does not change the position of the buffer pointer. If the editing buffer does not have sufficient space to accomodate the appended data, TECO issues the ?MEM error message. TECO terminates input begun by an A command when: 1. The end of the input file is reached; 2. A form feed character is read; 3. The buffer is 2/3 full and a line feed character is read; 4. The buffer is filled to within 128 characters of its capacity; or 5. The buffer is full. If TECO reads a form feed (i.e., if input stops because of condition 2), the form feed flag ^E is set to -1. TECO does not place the form feed character into the buffer with the rest of the text. The next input command you enter begins input of the character following the form feed. If a form feed is not read, the form feed flag is set to 0. You may test the form feed flag, but this is usually unnecessary. :A is equivalent to the A command except that a value is returned. -1 is returned if the append succeeded, and 0 is returned if the append failed because the end-of-the-input-file had previously been reached (^N flag is -1 at start of this command). [Not in TECO-8] n:A appends n lines of text from the input file to the contents of the text buffer. A value is returned indicating whether or not there were in fact n lines remaining in the input file. -1 is returned if the command succeeded. 0 is returned if end-of-file on the input file was encountered before all n lines were read in. Note that the command can succeed and yet read in fewer than n lines in the case that the text buffer fills up. [Not in TECO-8] Standard TECO PAGE 6-3 A (cont.) Note that nA, where n is a numeric argument, is a different command. If the end of the input file was previously read, that is, the EOF flag has been set (see ^N), the A command has no effect. Examples: *HKYA$$ This deletes the page of text currently in the editing buffer, and reads into the text buffer two pages of the current input file, appending the second page to the first. *A$$ This command enters the next page of the file into the editing buffer and appends it to the data already in the buffer. The previous contents of the buffer are not altered and the pointer is not moved. *EX$$ If the contents of a file fit into memory as a single unit, this command string will bring the entire file into memory and remove all form feeds. The ^N^; command will cause TECO to exit from the loop when the end-of-file flag is set. * If the contents of the file fit into memory as a single unit, this command string will bring the entire file into memory, preserving the page structure. Standard TECO PAGE 6-4 nA nA COMMAND ================================================================= Return the ASCII code of a character. FORMAT: nA where n points to the (n+1)th character following the buffer pointer. ================================================================= The purpose of the nA command is to return a number equal to the ASCII value for the (.+n+1)th character in the editing buffer. For example, the expression -1A is equivalent to the ASCII code for the character immediately preceding the pointer and 0A is equivalent to the ASCII code of the character immediately following the pointer. NOTE You cannot omit n. If you omit the position indicator, TECO will treat your command as an append command. Because TECO can not determine if you meant to type an nA or A command, no error message can be issued. If you attempt to reference a position outside of the buffer, TECO prints the ?POP error message. Example: 0A-^^/"E This command string segment will verify 1A-^^B"EMQ' ' that the string /B immediately follows the buffer pointer. If it does, TECO executes the macro in Q-register q. If not, TECO executes the commands following the second apostrophe. (The purpose of the ^^ command is to return the ASCII value of the character following it.) 0A-^^/ is an argument which is the value of the character following the pointer minus the ASCII value of a / character. NOTE Some TECO implementations ignore the value of n and treat the nA command like the 0A command. Thus, if you want to interchange macros with such implementations, you should only use the 0A command. Standard TECO PAGE 6-5 ^Atext ^Atext TYPE-OUT COMMAND ================================================================= Type delimited text. FORMAT: ^Atext @^A/text/ ================================================================= The ^Atext command types the "text" between the ^As on your terminal. The text is usually a message that you wish typed out during the execution of a command string or TECO program. The first ^A is the actual command. Enter it as a Caret-A or a . The second is a delimiter which indicates the last character in the text argument. The second delimiter must be a because a ^ is a legal character within a text string. The second format allows you to output text without worrying about typing an actual CTRL/A as terminator. The string "text" is the character string that TECO types out when it encounters the ^A command. The text string can contain any character except . Example: *0U1 %1=>EC$$ OUTPUTTING PAGE 1 OUTPUTTING PAGE 2 OUTPUTTING PAGE 3 OUTPUTTING PAGE 4 1. 0U1 stores 0 in Q-register 1. 2. The angle brackets indicate TECO will perform a repeated sequence of operations. 3. The 50S command searches for the 50th occurrence of a line feed. If the buffer does not contain 50 lines, the search fails and TECO executes the commands after the failure conditional ("F). 4. TECO appends the next page and branches back to search for the fiftieth line (AOST$). 5. If there are now 50 lines, TECO inserts a form feed into the buffer, and the text in the buffer up to and including the form feed is written to the output file. Standard TECO PAGE 6-6 ^A (cont.) 6. 0,.K removes this text from the buffer. 7. TECO then prints the message. 8. The %1 command increments the value in Q-register 1, then the = command prints it. 9. This continues until the end-of-file flag is set, that is, ^N=-1. 10. TECO closes the file. Standard TECO PAGE 6-7 B (beginning) B POSITION INDICATOR ================================================================= Position of beginning of buffer, always 0. FORMAT: B ================================================================= The B buffer position indicator always equals 0. It represents the position at the beginning of the buffer, that is, the position preceding the first character in the buffer. You may also use the B command in arithmetic expressions. Example: *B,.K$$ Remove all characters from the beginning of the buffer to the character immediately preceding the buffer pointer position. Standard TECO PAGE 6-8 ^B (current date) ^B RETURN THE CURRENT DATE COMMAND ================================================================== Return the current date. FORMAT: ^B ================================================================== ^B (caret/B) is equivalent to the current date via the following equations: OS/8: ^B = (((month*32)+day)*16)+((year-1970)&7)+k where k = 2048 if year>1977 and k=0 otherwise RT-11: ^B = (((month*32)+day)*32)+year-1972 RSTS/E: ^B = ((year-1970)*1000)+day within year RSX-11: ^B = ((year-1900)*16+month)*32+day VAX/VMS: ^B = ((year-1900)*16+month)*32+day TOPS-10: ^B = (((year-1964)*12+month-1)*31+day-1) Standard TECO PAGE 6-9 C (continue) C BUFFER POINTER COMMAND ================================================================= Move pointer forward. FORMAT: nC n:C (TECO-10 only) where n may be positive or negative. ================================================================= You use the C command to move the buffer pointer. You would normally use this command when the pointer only has to be moved across several characters. n:C same as nC except that a value is returned. If the command succeeded, -1 is returned. If the command failed, the pointer does not move and a value of 0 is returned. [TECO-10 only] The various forms of the C command are listed in Table 1. Table 1 C Commands Command Argument Function nC n>0 Move the pointer forward over n characters in the buffer from the current position of the pointer, i.e., nC is equivalent to (.+n)J. nC is also equivalent to -nR. C 1 is assumed Move the pointer forward one position. This is equivalent to -R. 0C 0 No movement of the pointer. -C -1 is assumed Move the pointer backward one position. This is equivalent to R. -nC -n<0 Move the pointer backward over n characters in the buffer from the current position of the pointer, i.e., nC is equivalent to (.-n)J. -nC is also equivalent to nR. If a C command (as opposed to a :C command) attempts to move the buffer pointer across either editing buffer boundary, TECO ignores the command and prints the ?POP error message. Standard TECO PAGE 6-10 C (cont) Examples: C Advance the buffer pointer one space. L4C Advance the pointer to the position following the fourth character in the next line. Q1C Advance the pointer the number of characters in Q-register 1. Standard TECO PAGE 6-11 ^C (terminate) ^C TERMINATE COMMAND ================================================================= Abort or exit. FORMAT: ^C ================================================================= ^C issued as a TECO command is a TECO command which aborts the present action and returns control to the operating system. Note that the first ^C may be entered in the up-arrow form, but that the second must be a real . A single ^C command not followed by a is not exactly the same on all implementations. Consult chapter V and the appendices for more details. Standard TECO PAGE 6-12 D (delete) D DELETE COMMAND ================================================================= Character deletion. FORMAT: nD n:D (TECO-10 only) where n may be positive or negative. ================================================================= The D commands permits you to individually delete characters and short strings. n:D same as nD but returns a value (-1 if command succeeds, 0 if command failed because the range of characters to be deleted fell outside the text buffer). [TECO-10 only] The various forms of the D command are listed in Table 2. Table 2 D Commands Command Argument Function nD n>0 Delete the n characters following the buffer pointer. D 1 is assumed Delete the character following the buffer pointer. 0D 0 This is a null command. -D -1 is assumed Delete the character preceding the buffer pointer. -nD -n<0 Delete the n characters preceding the buffer pointer. After TECO executes the D command, it positions the buffer pointer between the characters that preceded and followed the deletion. The pointer will always be adjacent to one of the characters to which it was adjacent before the deletion. If you attempt to delete text up to and across the beginning or end of the buffer, no text will be deleted and TECO prints the ?DTB error message. When deleting across carriage return/line feeds, the carriage return/line feed counts as two characters. Standard TECO PAGE 6-13 D (cont.) Examples: The following examples assume that the buffer contains ABCDE the text shown at the right; the buffer pointer points to FGHIJ the position between the M and the N. KLMNO PQRST UVWXY Z *6D$$ Deletes NO, the carriage return/line feed, and PQ, changing the third and fourth lines to KLMRST. *-D$$ Deletes M. *-5D$$ Deletes the carriage return/line feed, and KLM, changing the second and third lines to FGHIJNO. *-2D2D$$ Deletes LMNO, changing the third line to K. *KD$$ Deletes NO and the carriage return/line feed, and P, changing the third and fourth lines to KLMQRST. Standard TECO PAGE 6-14 ^D (decimal radix) ^D DECIMAL RADIX COMMAND [Not in TECO-10] ================================================================== Enter decimal mode FORMAT: ^D ================================================================== The entering of a ^D or a changes the current radix to decimal if TECO was not already in decimal. You would use this command after you have changed the radix to octal with a ^O command. If the radix is in decimal, this command is a no-op. The initial radix of TECO is decimal. Standard TECO PAGE 6-15 ^E (form feed flag) ^E END-OF-PAGE FORM FEED FLAG SIGNAL ================================================================== Flag which indicates if a form feed was read when the current buffer's contents were placed into the buffer. FORMAT: ^E ================================================================== If, when TECO is loading data into the editing buffer, input stops because a form feed was read, it sets the ^E flag to -1. If input was stopped because: 1. The end of the input file was reached; 2. The buffer is 2/3 full and a line feed character is read; 3. The buffer is filled to within 128 characters of its capacity; or 4. The buffer is full the ^E flag is set to 0. The P and other similar output commands test this flag to determine whether they should append a form feed to the contents of the buffer when they write the buffer's contents to the output file. Example: This macro divides a file into pages of 50 lines each. It also preserves original form feeds. EC$$ 1. TECO searches for the 50th line terminator. 2. If this search fails, TECO stores the value of the form feed flag in Q-register 1. 3. If this value is less than 0, TECO writes the buffer to the output file and reads in a new page. 4. If it equals zero, TECO appends a new page to the buffer's contents. 5. TECO then branches back to ST to again search for the fiftieth line. 6. If fifty lines were found, TECO appends a form feed. This text is written to the output file and then deleted. TECO again searches for the 50th line. 7. This continues until the end of the file is reached, i.e., ^N is set to -1. Standard TECO PAGE 6-16 EA (switch to secondary output) EA SWITCH TO SECONDARY OUTPUT COMMAND (Not in TECO-8, TECO-10 or RT-11) ================================================================== Switches the output to the secondary output stream. FORMAT: EA ================================================================== The EA command indicates to TECO that all output commands in future will refer to the secondary output stream. Thus after this another EW command can be entered which will open a secondary output file. To return to the primary output stream, EW$ should be entered as a command. (NOTE:TECO-8 and TECO-10 do not permit more than one output file to be open at one time.) This command does not open or close any file, nor does it change the contents of the text buffer. Standard TECO PAGE 6-17 EB (edit backup) EB EDIT BACKUP COMMAND ================================================================== Open an input and output file, creating a file with the same name as the input file. Upon completion of editing (e.g. EC command), the original input file will be preserved as a backup; the precise operation is operating system dependent. FORMAT: EBfilespec$ @EB/filespec/ :EBfilespec$ where / is an arbitrary delimiter which is not one of the characters in filespec. ================================================================== You use the EB command to open a file for editing in a manner similar to the TECO filespec command. NOTE You can only use this command for files stored on a directory-structured device. The EBfilespec command is equivalent to: *ERfilespec$EWfilespec$ except that the input file is preserved as a backup. The exact operation of the EB command is as follows: 1. The EB command executes an automatic ERfilespec$ command, opening the specified file for input and releasing any previously opened input file. 2. Then, it opens a temporary file to receive the output of the edited version of the input file. 3. The output device is the same as the input device. 4. Finally, the EB command sets an interal flag indicating that special action must be taken when the EB file is closed (by an EC, EF, EX, or EG command). It also prohibits any further EW or EB commands until the file is closed. The TECO filespec initialization command causes an automatic EBfilespec to be executed (followed by an automatic Y command). Standard TECO PAGE 6-18 EB (cont.) :EBfilespec$ executes the EB command, and returns a numeric value. -1 returned indicates success: the file is open for input. A 0 indicates the specified file could not be found, and no error message is generated. Other errors (e.g., hardware errors, protection violations, etc.) generate messages and terminate command execution as usual. Examples: *EBAB.FT$$ This command selects the disk file AB.FT for editing. When the editing is completed, the file AB.FT is the new version. TECO changes the old version to the backup file AB.BK, and deletes any previous backup file AB.BK. [OS/8 example] *@EB/DB1:TEXT.TXT/ This command selects the file TEXT.TXT;7 (assuming that version 7 is the latest version of TEXT.TXT on DB1) from device DB1:. This command creates the file DB1:TEXT.TXT;8. [RSX-11M example] Standard TECO PAGE 6-19 EC (exit close) EC EXIT CLOSE COMMAND ================================================================== Transfer the remainder of the input file to the output file, then close the input and output files. FORMAT: EC nEC (TECO-10 only) ================================================================== An EC commands TECO to write the contents of the editing buffer and any information in the input file and not as yet brought into the editing buffer onto the output file. The input and output files are closed. After the execution of an EC command, TECO remains in command mode. The EC command may be contrasted with the EX command which produces the identical output and also closes the input and output files. However, the EX command returns control to the operating system. The advantages of using an EC command instead of an EX command is that TECO does not have to be reloaded and you do not lose data in Q-registers. The nEC command can be used to make TECO reclaim lost space after it had expanded memory usage. nEC tells TECO to expand or contract until it uses nK words of memory. If this is not possible, then TECO's memory usage does not change. The 0EC command tells TECO to shrink back to its original size (use the least amount of memory possible). [TECO-10 only] Example: *EC$$ This command closes the current file, and writes its contents to the appropriate file. Standard TECO PAGE 6-20 ED (edit level) ED EDIT LEVEL FLAG ================================================================== Control various aspects of TECO's behaviour. FORMAT: ED Return value of flag. nED Set value of flag to n. m,nED In the flag, turn off those bits specified by m and turn on those bits specified by n. [Not in TECO-8] 0,nED Turn on the bits in the flag specified by n. [Not in TECO-8] m,0ED Turn off the bits in the flag specified by m. [Not in TECO-8] ================================================================== ED, the edit level flag, is a bit-encoded word that controls TECO's behavior in various respects. Any combination of the individual bits may be set as the user sees fit. The bits have the following functions: ED&1 allow caret (^) in search strings. If this bit is reset (off), a caret (^) in a search string modifies the immediately following character to become a control character. When this bit is set, a caret in a search string is simply the literal character caret. If you are editing a file that contains many caret characters (e.g., a RUNOFF file with case control), you will want to set this bit. ED&2 Allow all Y and _ commands. If this bit is set, the Y (Yank) command and _ (underscore or backarrow) command work unconditionally as described earlier in the manual. If reset (off), the behavior of the Y and _ commands are modified as follows: If an output file is open and text exists in the text buffer, the Y or _ command will produce an error message and the command will be aborted leaving the text buffer unchanged. Note that if no output file is open the Y and _ commands act normally. Furthermore, if the text buffer is empty the Y command can be used to bring in a page of text whether or not an output file is open (HKY will always work). The _ command will succeed in bringing one page of text into an empty text buffer but will fail to bring in successive pages if an output file is open. ED&4 When this bit is not set (0), TECO will try to expand memory as much as it can in order to try to fit entire pages into memory when requested to do so. If this bit is set (1), arbitrary memory expansion will not occur. In that case, TECO will expand memory if only necessary on the A command and not on the Y, P, or N commands. This bit is always set in TECO-10 and has no significance in TECO-8 or in TECO-11 on RT-11. ED&8 Reserved for future use. Standard TECO PAGE 6-21 ED (cont) ED&16 Allow failing searches to preserve dot. If this bit is set (1), then whenever a search fails, the original location of the text buffer pointer will be preserved. If this bit is off (0), then failing searches (other than bounded searches) leave the text buffer pointer at pointer position 0 after they fail. The initial value of ED&1 is system dependent (See appendices). The initial value of the other bits in the ED flag is 0. Standard TECO PAGE 6-22 EF (end file) EF END FILE COMMAND ================================================================== End the output file with the current page. FORMAT: EF ================================================================== The EF command is an output file closing command; that is, TECO closes the file you open with an EW command. You would normally use an EF command to close the output file after all output to it is complete. The EF command is most often used after a P command which outputs the last page of a file. NOTE If you type an EF command in the middle of the file, all succeeding pages that would have been read to it with an EX or EC command are omitted. If you are editing a file, it is far safer to exit with an EC command rather than an EF command because you could lose data if you mistakenly think you are at the end of the file. Examples: *PEF$$ Output the current page to the output file, then close the output file. Use this command string to close a file after writing the last page. *PWEF$$ Equivalent to the preceding example, except that the buffer is not altered. *EFEWTEXT.TE$$ Close the current output file and open an output file TEXT.TE on the system's default device. *ERPTR:$EFEWRXA0:FILE.MA$$ Read the input file from the paper tape reader, close the current output file, and open FILE.MA on RXA0: as an output file. Standard TECO PAGE 6-23 EF (cont.) *ERFILE.TX$EWFILE1.TX$ 4PEFEWFILE2.TX$ 4PEFEWFILE3.TX$EC$$ This command divides file FILE.TX into three files. The first two files each consists of four pages. The file FILE3.TX contains the remainder of FILE.TX. If you thought FILE.TX consisted of 12 pages of data, you could have concluded with a 4PEF command string, rather than an EC. However, if you were mistaken, you would not have written the remainder to an output file, and thus could lose all text following the 12th page with an EF command. Standard TECO PAGE 6-24 EG (exit and go) EG EXIT AND GO COMMAND ================================================================== Exit from TECO after output, then either 1. Reexecute the last compile-class CCL command, or 2. Perform the action specified in the optional text argument. FORMAT: EG$ @EG// EGtext$ @EG/text/ :EGtext$ etc. where text is a monitor command and / is an arbitrary delimiter which is not one of the characters in "text". ================================================================== The EG command is a dual purpose command. 1. It transfers the contents of the editing buffer and any remaining text in the input file to the output file. It then exits from TECO. This is identical to an EX command. 2. A monitor command or function will then be executed. If you specify a text argument to an EG command, that text must be a monitor command. After the exit from TECO, that command will be executed. Thus, *EGtext$ is equivalent to *EX .text This command form is often used when the text you have created is a batch command file. If it were, you would type EGSUBMIT filespec$$. If you do not specify a text argument, TECO will cause the last compile-class command (e.g., COMPILE, EXECUTE, or LOAD, etc.) attempted before TECO was called to be re-executed (with the same arguments). Generally, you would use the EG command to exit from an editing job that was called by an EBfilespec or TECO filespec command. Standard TECO PAGE 6-25 EG (cont.) As an example, suppose you give the command .COMPILE PLOT.FT to request compilation of a FORTRAN source program, but the compiler encounters errors in the code. You would then call TECO to correct these errors with the command: .TECO PLOT.FT After you have corrected the errors, you would exit from TECO with the command *EG$$ This command causes: 1) the rest of the file PLOT.FT to be output and closed; and 2) the command COMPILE PLOT.FT to be re-executed automatically. :EGtext$ performs the same function as the EC command, and then performs an operating system specific function. Consult the appendices for details. Example: The following is an example that can be called with a MUNG command. It will compile all FORTRAN programs that are on your disk. You call it with the OS/8 command .MUNG COMPIL,*.FT Z"E EBTEMP.TM$ Y3KZJ-3KJ I$JOB $ZJI$END $ EGSUBMIT TEMP.TM/T/H$ 'Z"N EWDIR.TM$ JI$JOB .DIR TEMP.TM<$ ZJI/F .MUNG COMPIL $END $ EGSUBMIT DIR.TM/H/T$' [[ NOT TESTED ]] In this example, the $ symbols indicates dollar signs rather than ESCAPEs. Standard TECO PAGE 6-26 EH (edit help) EH HELP LEVEL COMMAND ================================================================== Error message printing form command. FORMAT: nEH EH where n is an integer. ================================================================== TECO error messages consist of two parts. The first, or three-letter code, is always typed. By using the EH command, you may change TECO so that it prints either only the 3 letter code preceded by a ? or a more detailed description of the error. TECO always prints an error message. Table 3 lists the EH commands. Table 3 EH Commands Command Function 1EH Sets TECO so that it only prints the 3 letter code part of the error message. 2EH Sets TECO so that it prints both the three-letter error message code and the 1-line description automatically. 3EH Sets TECO so that it prints the three-letter error code, a brief one-line description, and a longer helpful paragraph of information. [In TECO-11, 3EH is equivalent to 2EH.] 0EH Resets TECO to the system standard mode of error message type out (normally equivalent to 2EH). EH#4EH If this bit of EH is set, the failing command is also output up to and including the failing character in the command followed by a question mark. (Just like TECO's response to the typing of a question mark immediately after an error.) This bit is not supported by TECO-10. You may return the current value of the EH setting by typing EH. To be useful, this must be typed as a numeric argument to another command. Standard TECO PAGE 6-27 EI (edit indirect) EI EDIT INDIRECT COMMAND (Not in TECO-8, TECO-10 or RT-11) ================================================================== Open/close a file as an Indirect Command File. FORMAT: EIfilespec$ @EI/filespec/ EI$ where / is an arbitrary delimiter which is not one of the characters in filespec. ================================================================== EIfilespec$ opens a file as an indirect command file, so that any further TECO requests for terminal input will come from this file. At end-of-file, or upon TECO's receipt of any error message, the indirect command file will be closed and terminal input will be switched back to the terminal. Note that this command only presets where input will come from; it does not "splice" the file's data into the current command string. While end-of-file closes the indirect command file, it does not automatically start execution of commands. Execution will begin only upon TECO's receipt of two adjacent ESCAPEs. All commands encountered in the indirect file will have their normal TECO meaning (as opposed to any immediate action meaning). For example, a encountered in an indirect file will not erase the command line in which it occurs. Instead, it will be treated as the TECO ^Uqtext$ command. The only exception to this rule is the command, which directs TECO to execute the preceding command string and then return to the indirect file at the point following the . EI$ - if an indirect command file is active, this command will close it and resume terminal input from the terminal. Any portion of the file after a double ESCAPE which has not yet been read is discarded. This command has no effect if no indirect file is already open. Standard TECO PAGE 6-28 EJ (environment characteristics) EJ RETURN ENVIRONMENT CHARACTERISTICS COMMAND ================================================================== Set/return various characteristics about the environment. FORMAT: nEJ k,mEJ (TECO-10 only) ================================================================== -1EJ returns a number representing the computer and operating system upon which TECO is currently running. This value has the form 256m+n where m is a number representing the computer in use and n is a number representing the operating system that is running. Current values of m and n are: Computer (m) Operating System (n) 0 PDP-11 0 RSX-11D 1 RSX-11M 2 RSX-11S 3 IAS 4 RSTS/E 5 VAX/VMS (compatibility mode) 6 RT-11 1 PDP-8 0 OS/8 2 PDP-10 0 TOPS-10 3 PDP-20 0 TOPS-20 4 VAX-11 0 VAX/VMS (native mode) 0EJ returns a value equal to your job number. On single-user systems, this is always a 0. 1EJ returns a value equal to your console keyboard number (the keyboard you detached from if you are running detached). On single-terminal systems, this is always a 0. 2EJ returns a value equal to your operating system's user identification number. This may be called your UIC, PPN, Group, etc. under various operating systems. Consult the appendices for more information. n,1EJ sets the terminal number to receive output. This will not affect terminal input. Your job will remain attached to, or detached from, your terminal, whichever it was before. Output will only occur if the specified terminal is ASSIGNed with a monitor ASSIGN command (you may ^C, issue that command and continue) and if your job has POKE privileges. This command also sets the terminal to be reattached if the set detach flag (64&ET) is cleared. The reattaching operation requires [1,2] or JACCT privileges. [TECO-10 only] n,2EJ sets your [p,pn] to n where n has the same format as the number returned by the 2EJ command. Issuance of this command requires the appropriate privileges. [TECO-10 only] Standard TECO PAGE 6-29 EK (exit kill) EK EXIT KILL COMMAND ================================================================== Detach output file from TECO without performing input or output. FORMAT: EK ================================================================== The EK command detaches the output file (if there is one). It does not delete any files. For example, if you type an EWfilespec1$ command and you decide that this is an error and you wish to write to filespec2 instead, then the command EKEWfilespec2$ will detach filespec1 without causing output. You can also use the EK command to detach a file if it were going to overwrite another file. Standard TECO PAGE 6-30 EL (write log) EL WRITE LOG COMMAND (TECO-10 only) ================================================================== Open the specified file for output as a log file. FORMAT: ELfilespec$ @EL/filespec/ where / is an arbitrary delimiter which is not one of the characters in filespec. ================================================================== Use ELfilespec$ to open the specified file for output as a log file. Any currently open log file will be closed. If the /APPEND switch is given, future logs will append to the file (if it already exists). The default is to supersede. All type-in to TECO and all type out from TECO goes into the log file. The log file is automatically closed by the EX and TECO commands. [TECO-10 only] Standard TECO PAGE 6-31 EN (edit next) EN EDIT NEXT COMMAND (Not in TECO-8, TECO-10 or RT-11) ================================================================== Initializes 'wild-card' lookup, or finds the next filespec that meets the previously specified wild-card characteristics. FORMAT: ENfilespec$ @EN/filespec/ EN$ :ENfilespec$ etc. where / is an arbitrary delimiter which is not one of the characters in filespec. ================================================================== ENfilespec$ presets the "wild card" lookup filespec. It is only a preset; it does not open, close, or try to find any file. The "wild card" lookup is the only filespec that can contain any wild card notations. See the appendices for the allowed wild fields in each operating system. EN$ - once the wild card lookup filespec has been preset, executing this command will find the next file that matches the preset wild card lookup filespec and will load the filespec buffer with that file's name. The G* command (q.v.) can be used to retrieve the fully expanded filespec. When no more occurences of the wild card filespec exist, the ?FNF error is returned. :EN$ executes the EN$ command, and returns a numeric value. A -1 indicates that another match of the wild card filespec exists and has been loaded into the filespec buffer. A 0 indicates no more occurences exist. No error message is generated. Standard TECO PAGE 6-32 EO (version) EO VERSION COMMAND ================================================================== Return version number of TECO. FORMAT: EO nEO (TECO-10 only) ================================================================== An EO command returns a value which specifies the current version number of TECO. If EO does not return the expected number, (7 for TECO-8, 1 for TECO-10, and 35 for TECO-11), this manual may contain inapplicable or erroneous information for your version. NOTE This command is included for compatibility with versions of TECO implemented on other DIGITAL computers. It is never used except to see if you have the version of TECO that this manual is describing. nEO - setting the value of the EO flag to n allows features that were peculiar to that version of TECO to work. [TECO-10 only] Standard TECO PAGE 6-33 EP (switch to secondary input) EP SWITCH TO SECONDARY INPUT COMMAND (Not in TECO-8, TECO-10 or RT-11) ================================================================== Switches the input to the secondary input stream. FORMAT: EP ================================================================== The EP command indicates to TECO that all input commands in future will refer to the secondary input stream. Thus after this another ER command can be entered which will open a secondary input file. To return to the primary input stream, ER$ should be entered as a command. (NOTE:TECO-8 and TECO-10 do not permit more than one input file to be open at one time.) This command does not open or close any file, nor does it change the contents of the text buffer. Standard TECO PAGE 6-34 EQ (edit into Q-register) EQ EDIT INTO Q-REGISTER COMMAND (TECO-10 only) ================================================================== Read the specified file into the specified Q-register. FORMAT: EQqfilespec$ @EQq/filespec/ where / is an arbitrary delimiter which is not one of the characters in filespec, and q is a Q-register. ================================================================== EQqfilespec$ reads specified file into Q-register q. No s or s are removed from the file, except that trailing s are discarded. The only switch permitted on the filespec in this command is the /DELETE switch, which causes TECO to delete the file after reading it, providing that the file is less than 500 characters long. This command supports the pseudo-device TMP:, for TMPCOR. Consult the appropriate appendix for details. [TECO-10 only] Standard TECO PAGE 6-35 ER (edit read) ER EDIT READ COMMAND ================================================================== Initializes a file so that TECO may sequentially extract information from it. FORMAT: ERfilespec$ @ER/filespec/ :ERfilespec$ etc. where / is an arbitrary delimiter which is not one of the characters in filespec. ================================================================== The ER command initializes a file so that TECO may read information from it. An ER command also terminates input from any file that may have been previously opened for input, in addition to opening a file for input. You may open one file for input, read only part of that file, and then, with another ER command, release the first file and open a new file for input. It is not necessary to read the end of one file before opening a second. However, opening the second file does end input from the first. :ERfilespec$ executes the ER command, and returns a numeric value. -1 returned indicates success: the file is open for input. A 0 indicates the specified file could not be found, and no error message is generated. Other errors (e.g., hardware errors, protection violations, etc.) generate messages and terminate command execution as usual. (NOTE:TECO-8 and TECO-10 do not permit more than one input file to be open at one time.) If you are creating a file, then you do not need to enter an ER command. Instead, you will enter the text directly into the text buffer from the terminal keyboard. Examples: *ERPULSE.FT$$ Select the file PULSE.FT from the system default device. *ERCDR:$EWPTP:$$ Select the card reader for input and the paper tape punch for output. *ERDTA1:INPUT.TX$EWRKA0:OUTPUT.TX$$ Open an input file INPUT.TX which is located on DECtape unit 1 and an output file OUTPUT.TX on disk unit 0. Standard TECO PAGE 6-36 ES (search verification) ES SEARCH VERIFICATION FLAG (Not in TECO-8) ================================================================== Control text typed out after searches. FORMAT: ES Return value of flag. nES Set value of flag to n. ================================================================== ES, the search verification flag, controls the text typed out after searches. If n is equal to 0, nothing is typed out after searches. If n is -1, the current line is typed out when a successful search at top level is completed (i.e., a V command is done automatically). If n is between 1 and 31, the current line is typed out with a line feed immediately following the position of the pointer to identify its position. If n is between 32 and 126, the current line is typed out with the ASCII character corresponding to the value of n immediately following the position of the pointer to identify its position. If you want to see more than one line of type out, use the form m*256+n. The n is the same as above. The m is the number of lines of view. For example, 3*256+^^! would be two lines on either side of the found line, and the found line with the character "!" at the pointer's position. The ES flag does not apply to searches executed inside iterations or macros; lines found inside iterations or macros are never typed out. [Not in TECO-8] The initial value of ES is 0. Standard TECO PAGE 6-37 COMMAND ================================================================== Throw away any numeric arguments. FORMAT: $ ^[ ================================================================== An if executed as a TECO command has no special effect other than discarding of numeric arguments. The is frequently used after an n%q command. You would use it to insure that the incremented value in the Q-register is not used as an argument for the following command. TECO echoes an as a dollar sign ($) on a terminal. On some terminals, ESCAPE is labeled ALTmode or PREfix. (The term "ALTMODE" is the traditional TECO name for ESCAPE). Standard TECO PAGE 6-38 ET (edit terminal) ET EDIT TERMINAL COMMAND ================================================================== Flag and command to set typeout modes. FORMAT: nET ET ================================================================== Use this command to control how TECO will type information to your terminal. The bit values this command can take are listed in Table 1. As these values represent bits, they are additive, that is, one ET value does not preclude another. Table 1 ET Commands Command Function ET&1 Type out in image mode. Setting this bit inhibits all of TECO's type out conversions. All characters are output to the terminal exactly as they appear in the buffer or ^A command. For example, the changing of control characters into the "caret/character" form, and the conversion of to $ (dollar sign) are suppressed. This mode is useful for driving displays. It should be used with caution, especially if you are talking to TECO over a dial-up line. ET&2 Process DELETEs and s in "scope" mode. Scope mode processing uses the cursor control features of CRT type terminals to handle character deletion by actually erasing characters from the screen. ET&4 Read lower case. TECO normally converts all lower case alphabetics to upper case on input. Setting this bit causes lower case alphabetics to be input as lower case. TECO commands and file specifiers may be typed in either upper or lower case. For the purpose of searches, however, upper and lower case may be treated as different characters. (See ^X flag). Standard TECO PAGE 6-39 ET (cont) ET&8 Read without echo for ^T commands. This allows data to be read by the ^T command without having the characters echo at the terminal. Normal command input to TECO will echo. ET&16 Cancel on type out. Setting this bit will cancel any outstanding when the next type out occurs. After TECO has canceled the , it will automatically reset the bit. ET&32 Read with no wait. This enables the ^T command to test if a character is available at the user terminal. If a character has been typed, ^T returns the value of the character as always. If no character has been typed, ^T immediately returns a value of -1 and execution continues without waiting for a character. ET&64 Detach flag (See appendices). ET&128 When this bit is set: 1) all informational messages are supressed, 2) any causes the immediate termination of TECO, and 3) any error causes the termination of TECO after the error message is printed. ET&256 If this bit is set, all lines output to the terminal are truncated to the terminal's width if needed. (RSTS/E, RSX-11, and VAX/VMS only.) ET&512 If this bit is set, the scope "WATCH" feature of TECO is present and your terminal is a scope type terminal. This bit is a read-only bit; its state cannot be altered. (See Section 5.17.) ET&1024 If this bit is set, the refresh scope "WATCH" feature of TECO is present and a refresh scope is available. This bit is a read-only bit; its state cannot be altered. (See Section 5.17.) ET&32768 If this bit is set and a is typed, the bit is turned off, but execution of the current command string is allowed to continue. This allows a TECO macro to detect typed s. In TECO-8, this bit is the 2048's bit rather than the 32768's bit. Standard TECO PAGE 6-40 ET (cont) The initial setting of ET is operating system dependent (See appendices). In addition, some of the ET bits are automatically turned off by certain error conditions. Example: The following example is a TECO command string to erase the entire screen of a VT52. 27^T^^H^TW7^T^^K^T$$ [[ NOT TESTED ]] Standard TECO PAGE 6-41 EU (edit upper/lower) EU EDIT UPPER/LOWER COMMAND ================================================================== Upper and lower case flagging of output. FORMAT: nEU where n is a positive, negative, or zero integer. ================================================================== The upper/lower case flag determines the manner in which TECO is to transmit characters to your terminal. If the terminal you are running on supports lower case input, TECO, when called into memory, sets this value to -1. Otherwise it will be set to 0. Use the nEU command to flag upper case output characters with an apostrophe ('). For example, if you are displaying a text, a form of the EU command will tell TECO to precede every character entered in lower case with an apostrophe. Although TECO prints the text in upper case, you would clearly be able to distinguish upper and lower case characters. The forms of the EU command are listed in Table 1. Table 1 EU Commands Command Argument Function nEU n>0 Flag upper cases characters with an apostrophe. 0EU 0 Flag lower case characters with an apostrophe. nEU n<0 Do not flag characters. Standard TECO PAGE 6-42 EV (edit verify) EV EDIT VERIFY FLAG (Not in TECO-8) ================================================================== Control text typed out. FORMAT: EV Return value of flag. nEV Set value of flag to n. ================================================================== EV, the edit verify flag, controls the text typed out before the TECO * prompt. If n is equal to 0, nothing is typed out. If n is -1, the current line is typed out (i.e., a V command is done automatically). If n is between 1 and 31, the current line is typed out with a line feed immediately following the position of the pointer to identify its position. If n is between 32 and 126, the current line is typed out with the ASCII character corresponding to the value of n immediately following the position of the pointer to identify its position. If you want to see more than one line of type out, use the form m*256+n. The n is the same as above. The m is the number of lines of view. For example, 3*256+^^! would be two lines on either side of the found line, and the found line with the character "!" at the pointer's position. [Not in TECO-8] The initial value of EV is 0. Standard TECO PAGE 6-43 EW (edit write) EW EDIT WRITE COMMAND ================================================================== Initialize the output file. FORMAT: EWfilespec$ @EW/filespec/ where / is an arbitrary delimiter which is not one of the characters in filespec. ================================================================== Use an EW command to open a file for output. If an output file is currently open, a second EW command closes that file before opening the new file. TECO only permits one output file to be active at any one time. If you type an EWfilespec command while a file is open, TECO deletes the previously opened file. TECO does not permit you to type an EW command if you had opened the file with an EBfilespec command. You may not output any information without first entering an EW or equivalent command. TECO does not permit you to use multiple EW commands without changing the input file. The MAKE filespec initialization command causes TECO to execute an automatic EWfilespec$ command. Examples: *ERRXA2:CREF.2$EWRXA0:CREF.3$$ This command string selects the file CREF.2 on diskette drive 2 for input and opens a file called CREF.3 on diskette drive 0 for output. If there is a file named CREF.3 already on the diskette, it will be overwritten. *EWPROG.PA$$ Prepare to write the output file PROG.PA on the system default device. *EWRXA1:OCON.TE$$ Prepare to write the output file OCON.TE on RXA1:. Standard TECO PAGE 6-44 EX (exit) EX EXIT COMMAND ================================================================== Exit from TECO to the operating system. FORMAT: EX ================================================================== The EX command is the easiest method for you to finish an editing job, with the latter part of the input file being properly output and the input and output files being closed. For example, you may be editing a 30-page file and the last change you make is on page 10. At this point you can give the command: *EX$$ . In this case, the action TECO performs is equivalent to the command string 21PEF, with an automatic exit to the monitor at the end. Thus, the action of TECO is: 1. To rapidly move all the rest of the input file, including the page currently in the buffer, to the output file; 2. To close the output file; and 3. To return control to the monitor. The EX command is equivalent to *EC$$ The EX command only outputs a form feed character if, after the output of the editing buffer's contents, it examines the ^E end-of-page form feed flag and finds that a form feed terminated input. In this way, the EX command maintains existing page sizes. Standard TECO PAGE 6-45 EY (unprotected yank) EY UNPROTECTED YANK COMMAND ================================================================== Read a new page into the editing buffer, irregardless of the setting of the ED flag. FORMAT: EY :EY (not in TECO-8) ================================================================== The EY command first clears the editing buffer and then reads text into the buffer until one of the following conditions is met. 1. The end of the input file is reached; 2. A form feed character is read; 3. The buffer is two-thirds full and a line feed is read; 4. The buffer is filled to within 128 characters of capacity; or 5. The buffer is completely filled. The usual effect of the Y command is to clear the editing buffer (execute an HK command) and then read the next page of the input file into it. Less than the entire next page is read in only if that page is too large to fit within two-thirds of the buffer's capacity. If the end of the input file has previously been read, the Y command only clears the buffer. If a form feed is read (i.e., if input stops because of condition 2), the form feed flag, ^E, is set to -1. TECO does not write the form feed into the buffer with the rest of the text. A succeeding input command begins input at the character following the form feed. If a form feed is not read, the form feed flag is set to 0, and the next input command begins input at the character following the last character previously read in. You may test the form feed flag, but ordinarily this is not necessary. :EY is the same as the EY command but a value is returned. -1 is returned if the Yank succeeded. 0 is returned if the Yank failed because the end-of-file had been reached on the input file prior to the initiation of this command. [Not in TECO-8] The EY command sets the buffer pointer to the position preceding the first character in the buffer. Standard TECO PAGE 6-46 EZ (edit write and zero) EZ EDIT WRITE AND ZERO COMMAND (TECO-10 only) ================================================================== Initialize the output file. FORMAT: EZfilespec$ @EZ/filespec/ where / is an arbitrary delimiter which is not one of the characters in filespec. ================================================================== Use the EZ command for outputting to magtapes and DECtapes, on which it initializes (zeros) the specified output device before switching the ouput to the primary output stream. In the case of a magtape, this command rewinds the magtape to load point. If the output device is a disk, this command works exactly like the EW command. [TECO-10 only] Standard TECO PAGE 6-47 E% (edit from Q-register) E% EDIT FROM Q-REGISTER COMMAND ================================================================== Create the specified file from the contents of the specified Q-register. FORMAT: E%qfilespec$ @E%q/filespec/ where / is an arbitrary delimiter which is not one of the characters in filespec, and q is any valid Q-register. ================================================================== E%qfilespec$ Create the specified file. The contents of the file will be the contents of Q-register q with no s deleted. No switches are permitted on the filespec of this command. This command supports the pseudo-device TMP:, for TMPCOR. Consult the appropriate appendix for details. [TECO-10 only] Standard TECO PAGE 6-48 E_ E_ DESTRUCTIVE SEARCH COMMAND ================================================================== Search for a character string and discard all pages before the string is found FORMAT: nE_text$ n@E_/text/ which n indicates what occurence of the string is to be found and / is an arbitrary delimiter which is not one of the characters in "text". ================================================================== The E_ command is identical to the _ command except that a E_ search does no protection checks. Generally, where the _ command executes a Y, the _ executes a EY. You use the E_ search for examination functions and for discarding parts of a file. You can also use the E_ command with a single numeric argument. The command nE_ causes a search for the nth occurrence of the search string. When you omit n, TECO assumes n=1. n must always be greater than 0. The E_ command may use a : modifier. and any of the match control characters defined in Chapter V. Example: *5E_VERSION88$$ This command can be used to determine if the string VERSION88 occurs in the input file five times. If it does, the pointer is positioned immediately after the fifth occurrence, and everything in the input file preceding the page on which the fifth occurrence is located, is discarded. If it is not, the entire file is is discarded. Standard TECO PAGE 6-49 ^F ^F COMMAND ================================================================== Return value of console switch register. FORMAT: ^F ================================================================== After you enter an ^F or command, TECO returns the number input on the console switch register. (On the PDP-12, this is the right switch register.) Standard TECO PAGE 6-50 n^F n^F RETURN TERMINAL NUMBER COMMAND (TECO-10 only) ================================================================== Return terminal number. FORMAT: n^F ================================================================== n^F n is the terminal number plus 200000 (octal) for job n's terminal. -1^F is the terminal number plus 200000 (octal) for your job's terminal. The result is 0 if the specified job is detached or if there is no such job. [TECO-10 only] Standard TECO PAGE 6-51 FB (bounded search) FB BOUNDED SEARCH COMMAND ================================================================== Perform a bounded search for a character string. FORMAT: nFBtext$ n@FB/text/ n:FBtext$ etc. m,nFBtext$ ================================================================== m,nFBtext$ performs the same function as the nStext$ command, but m and n (inclusive) serve as bounds for the search. In order for a search to be successful, the first character to match must occur between buffer pointer positions m and n. The string that is matched is permitted to extend beyond the search limits specified, provided that it begins within bounds. If mn, then the search proceeds in the reverse direction. nFBtext$ Performs a bounded search over the next n lines. If n is positive, the search proceeds forward over the next n lines; if n is negative the search proceeds backwards over the n preceding lines; if n is zero, the search proceeds backwards over the portion of the line preceding the pointer. Standard TECO PAGE 6-52 FC (bounded search/replace) FC BOUNDED SEARCH/REPLACE COMMAND ================================================================== Perform a bounded search for a character string and replace it. FORMAT: nFCtext1$text2$ n@FC/text1/text2/ n:FCtext1$text2$ etc. m,nFCtext1$text2$ ================================================================== m,nFCtext1$text2$ performs the same function as the nFStext1$text2$ command, but m and n (inclusive) serve as bounds for the search. In order for a search to be successful, the first character to match must occur between buffer pointer positions m and n. The string that is matched is permitted to extend beyond the search limits specified, provided that it begins within bounds. If mn, then the search proceeds in the reverse direction. nFCtext1$text2$ Performs a bounded search over the next n lines. If n is positive, the search proceeds forward over the next n lines; if n is negative the search proceeds backwards over the n preceding lines; if n is zero, the search proceeds backwards over the portion of the line preceding the pointer. In both cases, if text2 is omitted, the string, if found, is deleted. Standard TECO PAGE 6-53 FD (fast search/delete) FD FAST SEARCH/DELETE COMMAND (TECO-10 only) ================================================================== Search remainder of the editing buffer until text is found, then delete it. FORMAT: nFDtext1$ n@FD/text1/ where n is a positive number, and / is an arbitrary delimiter which is not one of the characters in text1. ================================================================== The FD command searches for a character string within the current editing buffer (function of the S command) and deletes it. If the string to be deleted is not found after the current pointer position and before the end of the buffer, the search fails and no deletion is made. If a search fails, TECO moves the buffer pointer to the beginning of the editing buffer. The FD command may use the a colon modifier. Text1 may use the match control characters described in Chapter V. Standard TECO PAGE 6-54 FK (fast search/kill) FK FAST SEARCH/KILL COMMAND (TECO-10 only) ================================================================== Search remainder of the editing buffer until text is found, then delete all text from start of buffer to new pointer position. FORMAT: FKtext$ @FK/text/ where n is a positive number, and / is an arbitrary delimiter which is not one of the characters in text. ================================================================== The FK command searches for a character string within the current editing buffer (function of the S command) and when found deletes all the text from the initial pointer position to the new pointer position. If the string is not found after the current pointer position and before the end of the buffer, the search fails and no deletion is made. If a search fails, TECO moves the buffer pointer to the beginning of the editing buffer. The FK command may use the a colon modifier. Text may use the match control characters described in Chapter V. Standard TECO PAGE 6-55 FN (fast non-stop search/replace) FN FAST NON-STOP SEARCH/REPLACE COMMAND ================================================================== Search remainder of the file until text is found, then replace it. FORMAT: nFNtext1$text2$ n@FN/text1/text2/ where n is a positive number. If text2 is omitted, no replacement occurs. / is an arbitrary delimiter which is not one of the characters in "text1" or "text2". ================================================================== Use an FN command to search for a character string in a page of the input file which may not yet have been read into the buffer (function of the N command) and to replace it with another string. The FN command operates like the N command when searching for the string. If the search fails, no replacement occurs. If you omit text2 in an FN search, TECO deletes text1 and does not insert a string into the buffer to replace it. However, even when text2 is omitted, its terminating delimiter must be present as shown in the form *FNtext1$$ The FN command, like all search commands, accepts a colon modifier. The text1 argument may contain the match control characters as described in Chapter V. If a search fails, TECO writes the entire input file to the output buffer. You may preface the FN command a number n to indicate which occurrence of a string is the object of the search. If a number specifying which occurrence of a string is to be replaced is less than 1, then TECO prints the error message ?NAS NEGATIVE OR ZERO ARGUMENT TO S. Standard TECO PAGE 6-56 FN (cont) Examples: *12FNSTRING$TEXT$$ This command replaces the twelfth occurrence of STRING with TEXT. *12$$ The first twelve occurrences of STRING are replaced with TEXT. Note the position of the ESCAPEs. The ESCAPE following the TEXT terminates the string TEXT. Because the search is within an iteration, a double ESCAPE cannot be used because it would terminate the command before the iteration were to be entered into the command string. *12<@FN/STRING//>$$ This is similar to the above example with the difference being that STRING is not replaced. If the @ modifier were not used, you would have to type $$. This would prematurely terminate the command and you would receive an error message. Standard TECO PAGE 6-57 FR (fast replace) FR FAST REPLACE COMMAND (Not in TECO-8) ================================================================== Replace the string just searched for or inserted with another. FORMAT: FRtext$ FR$ @FR/text/ @FR// where n is a positive number, and / is an arbitrary delimiter which is not one of the characters in text. ================================================================== FRtext$ is equivalent to "-nDItext$", where "n" is obtained from the most recent occurrence of the following: (a) the length of the most recent string found by a successful search command, (b) the length of the most recent text string inserted (including insertions from the FS, FN, or FR commands), or (c) the length of the string retrieved by the most recent "G" command. In effect, the last string inserted or found is replaced with "text", provided that the pointer has not been moved. [Not in TECO-8] @FR/text/ is equivalent to "FRtext$", except that "text" may contain ESCAPE characters. [Not in TECO-8] In either case if "text" is omitted the string is deleted. Standard TECO PAGE 6-58 FS (fast search/replace) FS FAST SEARCH/REPLACE COMMAND ================================================================== Search remainder of the editing buffer until text is found, then replace it. FORMAT: nFStext1$text2$ nFStext1$$ n@FS/text1/text2/ n@FS/text1// where n is a positive number, and / is an arbitrary delimiter which is not one of the characters in text1 or text2. ================================================================== The FS command searches for a character string within the current editing buffer (function of the S command) and replaces it with another string. If the string to be replaced is not found after the current pointer position and before the end of the buffer, the search fails and no replacement is made. If a search fails, TECO moves the buffer pointer to the beginning of the editing buffer. If you omit text2 from a FS command, text1 is deleted without replacement. However, when you omit text2, its terminating ESCAPE must be present as shown in the form: *FStext1$$ The FS command may use the a colon modifier. Text1 may use the match control characters described in Chapter V. You may preface the FS command with a number n to indicate which occurrence of a string is the object of the search. If the number specifying which occurrence of a string is to be replaced is less than 1, then TECO prints the error message ?NAS NEGATIVE OR ZERO ARGUMENT TO S. Examples: *12FSOF$FOR$$ This command causes TECO to search the current buffer for the 12th occurrence of the string "OF" and replace it with the string "FOR". *12$$ This command causes TECO to search for, then replace, the first 12 occurrences of OF with FOR. Note that the concluding double $$ follows the >. Standard TECO PAGE 6-59 FS (cont.) *12FSINTEREST$$ This command causes TECO to search the current page for the 12th occurrence of the string "INTEREST" and delete it. The two ESCAPEs, $$, must be typed following the string to be deleted; the first delimits the string for which you are searching and the second tells TECO that there is no replacement string. *@12FS/INTEREST//$$ This command is identical to the one described immediately above. This is very useful if a double ESCAPE would prematurely terminate your command string. Standard TECO PAGE 6-60 F' F' FLOW TO END OF CURRENT CONDITIONAL COMMAND (TECO-11 only) ================================================================== Flow to the end of the current current conditional. FORMAT: F' ================================================================== F' causes TECO to branch (flow) to the end of the current conditional. TECO effectively resumes execution at the first command following the ' at the end of the current conditional. Numeric arguments are eaten up by this command. If this command is issued while not in a conditional, the ?MAP error (or its equivalent) is issued. [TECO-11 only] Standard TECO PAGE 6-61 F< F< FLOW TO START OF ITERATION COMMAND (TECO-11 only) ================================================================== Flow to the start of the current iteration. FORMAT: F< ================================================================== F< causes TECO to branch (flow) to the start of the current iteration. TECO effectively resumes execution at the first command following the < at the beginning of the current iteration. The iteration count is not affected. If this command is issued outside of an iteration, it causes TECO to branch back to the start of the current command string (in the current macro level). [TECO-11 only] Standard TECO PAGE 6-62 F> F> FLOW TO END OF ITERATION COMMAND (TECO-11 only) ================================================================== Flow to the end of the current iteration. FORMAT: F> ================================================================== F> causes TECO to branch (flow) to the end of the current iteration. TECO effectively resumes execution at the matching >. The iteration count is tested as usual. If it has not expired, control returns back to the start of the iteration with the count having been incremented by 1. If the count was up, the iteration is exited and control continues with the first command after the >. If this command is encountered outside of an iteration, it has the same effect as the command. [TECO-11 only] Standard TECO PAGE 6-63 F_ (fast non-stop search/replace) F_ FAST NON-STOP SEARCH/REPLACE COMMAND (not in TECO-10) ================================================================== Search remainder of the file until text is found, then replace it. FORMAT: nF_text1$text2$ n@F_/text1/text2/ where n is a positive number. / is an arbitrary delimiter which is not one of the characters in "text1" or "text2". ================================================================== Use an F_ command to search for a character string in a page of the input file which may not yet have been read into the buffer (function of the _ command) and to replace it with another string. The F_ command operates like the _ command when searching for the string. If the search fails, no replacement occurs. If you omit text2 in an F_ search, TECO deletes text1 and does not insert a string into the buffer to replace it. However, even when text2 is omitted, its terminating delimiter must be present as shown in the form *F_text1$$ The F_ command, like all search commands, accepts a colon modifier. The text1 argument may contain the match control characters as described in Chapter V. You may preface the F_ command a number n to indicate which occurrence of a string is the object of the search. If a number specifying which occurrence of a string is to be replaced is less than 1, then TECO prints the error message ?NAS NEGATIVE OR ZERO ARGUMENT TO S. Standard TECO PAGE 6-64 F| F| FLOW TO ELSE CLAUSE OF CURRENT CONDITIONAL COMMAND (TECO-11 only) ================================================================== Flow to the else clause of the current conditional. FORMAT: F| ================================================================== F| causes TECO to branch (flow) to the else clause of the current conditional. TECO effectively resumes execution at the first command following the | at the end of the current THEN clause. If the current conditional has no ELSE clause, or if an unmatched ' is encountered before an unmatched |, then control resumes at the command following the ' . Numeric arguments are eaten up by this command. If this command is issued while not in a conditional, the ?MAP error (or its equivalent) is issued. Well-structured programs should not need to use this command. [TECO-11 only] Standard TECO PAGE 6-65 Gq (get) G GET COMMAND ================================================================== Place Q-register q's contents in the editing buffer, or type it out. FORMAT: Gq :Gq where q is a Q-register. ================================================================== The command Gq (where q is one of the 36 Q-registers) fetches a copy of the character string stored in the Q-register and inserts it into the editing buffer at the current buffer pointer position. This command does not alter the contents of the Q-register. TECO positions the buffer pointer at the right end of the character string inserted. Examples: *ZJ-5XAJ8LGA$$ This command string puts a copy of the last five lines of the page into Q-register A and then puts a copy of these five lines immediately after the eight lines in the page. It does not delete the five lines from their position at the end of the page. If you type a : before a Gq command, TECO types the contents of that register on your terminal without inserting it into the buffer. Standard TECO PAGE 6-66 H (wHole) H WHOLE POSITION INDICATOR ================================================================== Incorporate entire buffer (B,Z) limits into a command argument FORMAT: H ================================================================== The H command is equivalent to the numeric pair B,Z. Thus, in those commands that take two numeric buffer position arguments, H represents the combination B,Z (which is the entire buffer). This letter is particularly useful with type-out and output commands. Examples: *HK$$ Delete entire editing buffer. *HT$$ Type entire buffer. *HXA$$ Insert entire buffer into Q-register A. Standard TECO PAGE 6-67 ^H ^H RETURN TIME OF DAY COMMAND ================================================================== Return the current time of day. FORMAT: ^H ================================================================== ^H (caret/H) is equivalent to the current time of day via the following equations: OS/8: ^H = 0 RT-11: ^H = 0 RSTS/E: ^H = minutes until midnight RSX-11: ^H = (seconds since midnight)/2 VAX/VMS: ^H = (seconds since midnight)/2 TOPS-10: ^H = 60ths of a second since midnight (or 50ths of a second where 50 Hz power is used) Standard TECO PAGE 6-68 I (insert) I INSERT COMMAND ================================================================== Insert text into the buffer FORMAT: Itext$ @I/text/ where text is only limited by available command string storage space and / is an arbitrary delimiter which is not one of the characters in "text". ================================================================== The I command followed by a text argument is the basic TECO insertion command. Delimit the text argument by an ESCAPE. This command inserts the ASCII text string, "text", into the editing buffer just ahead of the buffer pointer. After the insertion, TECO positions the buffer pointer immediately after the last inserted character. TECO does not insert the ESCAPE terminating the text argument. "text" may contain any character except the special characters listed in Table 1-1. The number of characters in the text is limited by the amount of core available for command string storage. During normal editing jobs, DIGITAL recommends that you limit insertions to about 10 to 15 lines each. If a very long insertion command begins to exceed the TECO command storage capacity, TECO rings the terminal bell once when ten characters of storage remain and once after each additional character entered. The bell also echoes as a ^G. When this occurs, terminate the command string immediately. Entering more than 10 additional characters into the current command string causes a fatal error. The @I/text/ command is slightly more powerful than the I command. It enables you to insert single (but not double) ESCAPE characters in addition to the characters that can be inserted with the I command. The @I form is useful for inserting TECO command strings into the editing buffer. Delimit the text argument to the @I command, both before and after, by any single character which is not itself a part of the text to be inserted. TECO does not require an ESCAPE to terminate the text string; it is the second occurrence of the delimiting character that terminates the text string. The text is inserted immediately preceding the buffer pointer, as it is with the I command. TECO does not insert the delimiting character. Standard TECO PAGE 6-69 I (cont.) Examples: *JIline one This example shows insertion of several lines line two of text at the beginning of the buffer. line three $$ * *KI Use this command string to delete the tail of $$ a line without removing the carriage return/ * line feed at the end. If the buffer contains ABCD EFGH and the buffer pointer is between the B and the C, this command produces AB EFGH *I Use this command to insert a carriage return without a line feed following it. The single $$ deletes the line feed but not the * carriage return. *@I%TEXT$x$%$$ This is a convenient method for inserting multiple ESCAPEs when using the @I command. Type the sequence x, where x is any character except an ESCAPE, between the successive ESCAPEs. If the x were not typed, TECO would assume that you were terminating the command string. The following examples assume that the buffer contains ABCDEF with the buffer positioned between the D and E. *IXYZ$$ Produces ABCDXYZEF with the buffer pointer be- tween the Z and the E. *I Produces ABCD $$ EF with the buffer pointer positioned before the E. *3RI $4CI $$ Produces A BCDE F Standard TECO PAGE 6-70 nI$ (Insert character) nI$ INSERT CHARACTER COMMAND ================================================================== Insert a character into the buffer. FORMAT: nI$ n@// where n is the ASCII value of the character to be inserted. ================================================================== The nI$ command inserts one character into the editing buffer. The n numeric argument includes all characters that the I and @I commands cannot insert. However, the nI$ command inserts only one character at a time. The command nI$ inserts the character with the ASCII value n into the buffer immediately preceding the pointer. NOTE The I$ command inserts a null string into the editing buffer. This is very different from an nI$ command which always inserts a character into the buffer. The nI$ command is most often used to insert the special characters that are filtered out byt he operating system (see table 3-3). Example: If you are creating a macro that you wish to abort immediately if a certain condition occurs, then you could type some command string minus the and then add it with the insert command, i.e., *IABCDEFGHIJKILMN$$ If the were to be inserted after the K, then the command string *3R3I$HXA$$ would insert the ^C, then place the command string in Q-register A. This command string could also be typed *IABCDEFGHIJK$ 3I$ ILMN$$ Standard TECO PAGE 6-71 , see Standard TECO PAGE 6-72 J (jump) J JUMP COMMAND ================================================================== Move buffer pointer relative to the beginning of the buffer. FORMAT: nJ n:J (TECO-10 only) where n>0 ================================================================== The nJ command moves the buffer pointer to the position immediately after the nth character in the buffer. The various forms of the J command are listed in Table 1. n:J same as the nJ command except that if pointer position n is outside of the buffer, the pointer does not move and a value of 0 is returned. If the command succeeded, a value of -1 is returned. [TECO-10 only] Table 1 J Commands Command Function nJ Move pointer to position following the nth character in the text buffer. 0J Move the pointer to the beginning of the buffer. J Equivalent to 0J. ZJ Move the pointer to the end of the buffer. Standard TECO PAGE 6-73 K (kill) K KILL COMMAND ================================================================== Line deletion. FORMAT: nK m,nK where n may be positive, negative, or zero if there is one argument. If there are two arguments, m0 Deletes everything from the buffer pointer through the nth line terminator following it. 0K 0 Deletes everything from the pointer back to the beginning of the current line. -K -1 assumed Deletes everything from the pointer back to the beginning of the line preceding the current line. nK n<0 Deletes everything from the pointer back to the beginning of the nth line preceding the current line. m,nK m0 Advances the pointer to the beginning of the nth line following the current line. 0L 0 Moves the pointer back to the beginning of the current line. -L -1 assumed Moves the pointer back to the beginning of the line preceding the current line. -nL -n<0 Moves the pointer back to the beginning of the nth line preceding the current line. If you attempt to move the buffer pointer backward beyond the position immediately prior to the first character in the buffer, or forward beyond the position immediately after the last character in the buffer, TECO does not print an error message; however, TECO moves the pointer to the beginning or end of the editing buffer. Standard TECO PAGE 6-76 L (cont.) Examples: *J3L$$ The J command moves the pointer to the beginning of the first line in the buffer. The 3L command then moves it to the beginning of the fourth line. *ZJ-2L$$ The ZJ command moves the pointer to the end of the last line in the buffer. Then the -2L command moves the pointer to the beginning of the next to last line in the buffer (assuming that the last line is terminated by a line feed). *L4C$$ Advance the pointer to the position following the fourth character in the next line. Standard TECO PAGE 6-77 M (macro) M MACRO COMMAND ================================================================== Execute the command string stored in a Q-register. FORMAT: Mq nMq m,nMq where q is a Q-register ================================================================== TECO command strings are composed of ASCII character and, as such, you can insert or read them into the editing buffer just like any other text. The command string stored in a Q-register is called a macro. When a command string is in the editing buffer, you can edit it. However, you may not execute it because, when it is in the buffer, it appears to be data to TECO. However, if you copy a command string from the editing buffer into a Q-register (using an X command), then this command string can be executed. The command Mq (where q is one of the 36 Q-registers) executes the text in that register. Thus, entering an Mq command is analogous to calling a subroutine. You may include any TECO command in the command string which is stored in and executed from the Q-register. The only restriction is that the commands must all be complete within the macro in the Q-register. For example, a command and its argument must not be split apart, one in the command string and the other in the Q-register. If you include iterations and conditional execution strings these must also be complete within the register. If you use an O command in the macro, the tag to which it branches must also be in the register. The forms of the M command are: Mq Execute the contents of Q-register q. nMq Execute the contents of Q-register q and use n as a numeric argument for the first command in the command string. m,nMq Execute the contents of Q-register q and use m,n as a numeric argument for the first command in the command string. Standard TECO PAGE 6-78 M (cont.) Example: The following shows the creation of a macro to format a file into pages of 50 lines. The macro will be stored in a Q-register, then be called to operate upon two files. *EWFIFTY.TEC$$ *@I/Y EC/$$ *HXA$$ *EC$$ *EBFILE1.FOR$$ *MA$$ *EBFILE2.FOR$$ *MA$$ * 1. This macro will be kept after it is created in the file FIFTY.TEC. 2. The Y brings in the first page of text. 3. The ^N will signal if the end-of-file flag has been set. 4. If it has been set, ^N; will cause a branching from the iteration. 5. If the page has fewer than fifty lines, a new page is appended to the buffer and the loop is continued. 6. If there are at least 50 lines, a form feed is appended, the 50 lines are output, then killed. 7. This will continue until the ^N flag is set, indicating the end of the file has been reached. 8. AFter the macro has been completed, it is stored with the HXA command into Q-register A. 9. FIFTY.TEC is then closed. 10. FILE1.FOR is then opened, and the Q-register is executed. 11. The procedure is repeated for FILE2.FOR Standard TECO PAGE 6-79 N (non stop search) N NON-STOP SEARCH COMMAND ================================================================== Search a file for a string until it is found. FORMAT: nNtext$ n@N/text/ where n>0 and / is an arbitrary delimiter which is not one of the characters in "text". ================================================================== The N command combines the S command with input/output functions. Use the N command to search for a character string in a page of the input file which may not yet have been read into the editing buffer. The N command may accept a colon modifier. "text" may include the match control characters described in Chapter V. The N command differs from the S command in that it does not terminate at the end of the page currently in the buffer. If TECO does not find a match for the search string between the current buffer pointer position and the end of the buffer, the current page is output, the buffer is cleared, and the next page is read in. The search then starts over at the beginning of the new page. This process continues until a match is found or the input file is completely written to the output file. If an N search fails, the entire input file passes through the buffer and is written to the output file. TECO also clears the editing buffer but does not close the output file. Unless the : modifier was used or the search is within an interation, an error message is typed to notify the user that the search has failed. An N search can not detect a match when the matching characters are split across two buffer. It also can not detect a match if the characters are on separate lines unless you include the line separator in the search string. The output function of the N command is exactly like the P command. If a form feed character was encountered when a given page was read in, TECO appends a form feed character to that page when it is output; otherwise no form feed character is output. Standard TECO PAGE 6-80 N (cont.) If you do not include a text argument with a search command, e.g., N$$, TECO executes the search using the last previous search command argument. You may use the N command with a single numeric argument. The command nN causes a search for the nth occurrence of the search string. When you omit n, TECO assumes n=1. n must be greater than 0. The _ search differs from the N search in that the _ search produces no output. However, both will search through the entire file following the buffer pointer until a match occurs. Examples: *NDIGITAL$$ If page 5 of the text is currently in the buf- fer and the string DIGITAL does not occur un- til page 15, this command causes pages 5 through 14 to be output and page 15 to be read in. The pointer will be set immediately after the L in DIGITAL. *NLAST LIN PG1 If this string actually exists in the file but 1ST LIN PG2 the two lines are not read into the same buf- $$ fer, the N search will fail. In other words, ?SRH FAILED a search can be dependent on how TECO brings * information into the buffer. *NMASSACHUSETS$$ ?S?SRHLED An N search should not be used when an S *EF$$ search would suffice, becaus user errors with *EBOUTPUT.FI$$ the N command, such as the spelling shown *Y$$ here, can cause considerable delay. In this *NMASSACHUSETTS$$ example, the error causes two passes over the entire file instead of just one. Standard TECO PAGE 6-81 ^N (end-of-file) ^N END-OF-FILE FLAG ================================================================== Flag that indicates if the end-of-file has been reached. FORMAT: ^N where the command can be entered as a or Caret-N ================================================================== The ^N command returns a value indicating if the end of the file has been reached. It is most often used in conjunction with a command that inputs data. The setting of the flag will then be the cause of jumping from an iteration or the fulfillment of a condition for a conditional execution command. It is initially set to 0. When the end-of-file has been reached, it is set to -1. Example: *$$ each page of a file. *<^N^_; P> EX$$ This macro changes all occurences of ABC to DEF and all occurences of XYZ to PQR in an entire file. The ^N terminates the iteration when the ^N flag is set to -1. Standard TECO PAGE 6-82 O (goto) O GOTO COMMAND ================================================================== Unconditional branch to a location. FORMAT: Otag$ @O/tag/ (not in TECO-8) nOtag0,tag1,tag2...$ (TECO-11 only) n@O/tag0,tag1,tag2.../ (TECO-11 only) where tag is composed of ASCII characters delimited by exclamation marks in the command string and by an ESCAPE in the O command. ================================================================== The purpose of the tag following the O is to name the destination of the unconditional branch instruction. The tag location itself may be either before or after the O command in the command string. However, the branch cannot be before the beginning of the current iteration. For example, if you enter the following command string: . . .!tag1!. . .<. . .Otag1$. . .> TECO will produce an error message. However, the command string segment . . . is legal. The O command causes the command string execution pointer to be moved to the first character following the exclamation point that terminates the tag, and command execution continues from that point. @O/tag/ is equivalent to Otag$ except that a delimiter (shown here as /) is used before and after the specified tag. Any character other than that delimiter is permitted inside the tag. The usual string build characters are permitted when specifying the tag. [Not in TECO-8] nOtag0,tag1,tag2,...$ causes TECO to branch to the tag specified by the nth tag in the accompanying list. The string argument to this command consists of a sequence of tags separated by commas. The tags may contain any characters other than comma or , however good programming practice dictates that the tags should consist only of letters and digits. There must be no intervening spaces since these would be considered part of the tag. If n is out of range, then command execution continues with the first command following the that delimits this command. [TECO-11 only] n@O/tag0,tag1,tag2,.../ Same as the preceding command except that the list of tags is bracketed by a delimiter shown here as "/". The delimiter can be any character that does not appear within the list of tags. In particular, using comma for the delimiter would not be very useful. [TECO-11 only] Standard TECO PAGE 6-83 O (cont) Tags are ignored except when an O command forces TECO to scan the command string from them. There is no restriction on the length of the tag (except that it must fit into the buffer). The tag must also be in the same macro level, i.e., you cannot branch from within a called macro to outside of the contents of the Q-register nor can you branch from outside of a macro into it. Standard TECO PAGE 6-84 (octal radix) OCTAL RADIX COMMAND ================================================================== Change to octal radix. FORMAT: ^O ================================================================== The entering of a ^O or changes the current radix to octal if TECO was not already in octal. If the radix is in octal, this command is a no-op. The intial radix of TECO is decimal. Standard TECO PAGE 6-85 P (page) P PAGE COMMAND ================================================================== Write the buffer's contents to the output file. FORMAT: nP m,nP :P (not in TECO-8) where n may be positive, negative, or zero if there is one argument. If there are two arguments, m0 Executes the P command n times. This comand can be used to skip over several pages of text when no editing is required. The nP command causes the n pages of the input file, starting with the page currently in the editing buffer, to be output, and then the nth page after the current page to be brought in. Standard TECO PAGE 6-86 P (cont.) m,nP m0 if there is one argument. If there are two arguments, m0) outputs n copies of the text in the buffer, appending a form feed to each copy. The PW command does not clear the buffer nor does it move the buffer pointer. (The same is also true of a P command used with two arguments.) Note also that when you use a PW command with a single argument, a form feed character is always automatically sent to the output file immediately following the data from the buffer. TECO appends the form feed character to the outgoing data regardless of whether or not it encountered a form feed character when the data was read in, i.e., regardless of the setting of the ^E form feed flag. This is not true of the P command. Table 1 lists the various forms of the PW command. Table 1 PW Command Command Argument Function PW 1 is assumed Writes the contents of the buffer onto the output file and appends a form feed character. The buffer is not cleared and the pointer position remains unchanged. nPW n>0 Same as n. This executes the PW command n times. Standard TECO PAGE 6-88 PW (cont.) m,nPW m0 Move the pointer backwards over n characters in the buffer from the current buffer pointer position. nR is equivalent to -nC. R 1 is assumed Move the pointer backward one character. 0R 0 This is a null command. -R -1 is assumed Move the pointer forward one character. This is equivalent to C. -nR -n<0 Move the pointer forward over n characters in the buffer from the current buffer pointer position. -nR is equivalent to nC. If an R command attempts to move the pointer across either buffer boundary, TECO ignores the command and prints the ?POP error message. Example: *0L2R$$ The 0L command moves the pointer back to the beginning of the current line. Then, the 2R command moves it back past the last two characters in the preceding line (i.e. back over the pair that are normally found at the end of a line. Standard TECO PAGE 6-91 TEST/RESET CURRENT RADIX COMMAND (TECO-11 only) ================================================================== Reset the current radix, or return its current value. FORMAT: ^R n^R where n may only be one of 8, 10 or 16. ================================================================== ^R returns the binary value of TECO's current radix. [TECO-11 only] n^R sets TECO's radix to the value of n. It is currently implemented only in TECO-11, where n may only be one of the values 8, 10, or 16 (representing octal mode, decimal mode, or hexadecimal mode). If n is not one of these values, TECO's radix remains unchanged and the ?IRA error message is produced. (Note that if the current radix is octal, the above three values become 10, 12 and 20.) Standard TECO PAGE 6-92 S (search) S SEARCH COMMAND ================================================================== Search for a character string. FORMAT: nStext$ n@S/text/ n:Stext$ etc. m,nStext$ ::Stext$ ================================================================== Use the S command to search for a character string within the current editing buffer. If the string is not found between the current buffer pointer position and the end of the buffer, the search fails. After an unsuccessful S search, the buffer pointer is reset to the beginning of the buffer, and, unless you had used the : modifer or the search is within an iteration, TECO prints message. Type the search string as an alphanumeric argument following the S. Terminate it with an ESCAPE. "text" can contain any character except those listed is Table 1-1, Special Characters. The S command may be used with a single numeric argument. The command nS causes a search for the nth occurrence of the specified search string. When n is omitted, n=1 is assumed. If n is less than 0 a reverse search is done. m,nStext$ is a system specific command. Consult Appendix C. ::Stext$ is a compare command. It is not a true search. If the characters in the buffer immediately following the current pointer position match the search string, the pointer is moved to the end of the string and the command returns a value of -1; i.e., the next command is executed with an argument of -1. If the characters in the buffer do not match the string, the pointer is not moved and the command returns a value of 0. Identical to ".,.:FBtext$". If you are searching for text that contains an ESCAPE, you can use an @ modifier to the S command. If you do not include a text argument with an S command, e.g., S$$, TECO executes the search using the last previous search command argument. The S command may use the match control characters described in Chapter V. Standard TECO PAGE 6-93 S (cont.) Examples: *SAB$$ This causes the pointer to be positioned immediately after the B, in the first occurrence of the string AB after the current position of the pointer. *SNIX$$ The string NIX is not found between the ?SRH SEARCH FAILED current pointer position and the end of the buffer. The error message is typed and the pointer is moved to the beginning of the buffer. You may have typed an incorrect search string, the pointer may have been positioned somewhere in the buffer after the N, or the string NIX may not be in the editing buffer. *@3S+$+IEF$$ The command @3S+$+ searches for the third occurrence of the ESCAPE character following the buffer pointer. When this ESCAPE is found, the characters EF are inserted immediately after it. The + characters serve as the delimiters for the one-character search string $. The + characters are not part of the search string. Standard TECO PAGE 6-94 ^S (length of last string) ^S RETURN LENGTH OF LAST STRING COMMAND (Not in TECO-8) ================================================================== Return negative of length of last string inserted or found. FORMAT: ^S ================================================================== ^S (caret/S) is equivalent to the negative of the length of the last insert, string found, or string inserted with a "G" command, whichever occurred last. To back up the pointer to the start of the last insert, string found, etc., type "^SC". Standard TECO PAGE 6-95 T (type) T TYPE COMMAND ================================================================== Type out text in the editing buffer. FORMAT: nT m,nT where n may be positive, negative, or zero. ================================================================== You can type any part of the text in the editing buffer for examination by using the T command. The text TECO types depends on the position of the buffer pointer and the argument(s) given. The T command never moves the buffer pointer. When preceded by a single numeric argument, T is a line-oriented command; when preceded by a pair of numeric arguments, T is a character-oriented command. The T command variations are described in Table 1. Table 1 T Commands Command Argument Function T 1 assumed Type out everything from the buffer pointer through the next line terminator. If the pointer is at the beginning of a line, T causes the entire line to be TECO typed out. If the pointer is in the middle of a line, T causes that portion of the line following the pointer to be typed out. nT n>0 Type out everything from the buffer pointer through the nth line terminator following it. If the pointer is at the beginning of a line, this command types out the next n lines (including the current line). 0T 0 Type out everything from the beginning of the current line up to the pointer. This command is especially useful for determining the position of the buffer pointer. -T -1 assumed Types out everything in the line preceding the current line, plus everything in the current line up to the pointer. Standard TECO PAGE 6-96 T (cont.) nT n<0 Types out everything in the n lines preceding the current line, plus everything in the current line up to the pointer. m,nT m0 Types the n characters immediately following the buffer pointer. .-n,.T n>0 Types the n characters immediately preceding the buffer pointer. HT H=B,Z Types out the entire contents of the buffer. Examples: The following examples assume the buffer contains the text ABCDE shown at the right, with the buffer pointer positioned be- FGHIJ tween the M and the N. KLMNO PQRST UVWXY Z *T$$ NO *3T$$ NO PQRST UVWXY *0T$$ Note that no carriage return/line feed exists KLM* between the beginning of the line the pointer is on and the pointer itself, therefore, none is typed. The second asterisk indicates that TECO is ready for the next command. *0TT$$ This pair of commands causes the line to be typed KLMNO out without moving the pointer. *-2T$$ ABCDE FGHIJ KLM* *.,.+6T$$ The six characters typed are NO, carriage return/line NO feed, and PQ PQ* *.-2,.T$$ LM *0LT$$ This pair of commands types out the entire current line KLMNO and leaves the pointer at the beginning of the line. Standard TECO PAGE 6-97 ^T (type in) ^T TYPE-IN COMMAND ================================================================== Use the ASCII code for the next character typed at the terminal as an argument. FORMAT: ^T ================================================================== ^T is equivalent to the ASCII code for the next character you type at the terminal. When TECO executes a command string, every ^T character encountered causes it to pause and accept one character typed at the terminal. TECO then substitutes the ASCII code for this character for the ^T. This command is only useful as a numeric argument for another command. It is often used with an ^Atext message string preceding it. The message string inform the user that TECO is waiting for a character to be typed in. Example: *$$ serts the letter which is typed in following FUNCTION LETTER M each occurrence of the string FUNCTION that is FUNCTION LETTER N found by the search command. FUNCTION LETTER C *^TUC$$ Places the ASCII value of the typed character Q-register C. Standard TECO PAGE 6-98 ^T (type out) ^T TYPE-OUT COMMAND ================================================================== Type out the character whose ASCII code precedes the command. FORMAT: n^T where n is the ASCII code for a character ================================================================== The n^T command types out the character whose ASCII code is n. Example: *J$$ to type the next line. Standard TECO PAGE 6-99 (insert) INSERT COMMAND ================================================================== Insert followed by text into editing buffer. FORMAT: text$ ================================================================== The tab command is equivalent to the I command, except that the tab command causes TECO to insert the tab itself as well as all the following text up to the ESCAPE. In other words, if the first character of a text string to be inserted by an I command is a tab, you may omit the I. The number of characters in the text is limited by the amount of memory available for command string storage. During normal editing jobs, DIGITAL recommends that you limit insertions to about 10 or 15 lines each. If a long insertion command begins to exceed the TECO command storage capacity, TECO rings the terminal bell once when ten characters of storage remain and once after each additional character entered. When this occurs, terminate the command string immediately. Entering more than 10 additional characters into the current command string causes a fatal error. Example: If the buffer contains ABCDEF with the buffer pointer positioned between the D and E, then *XYX$$ produces ABCD XYZEF The pointer is now between the Z and E Standard TECO PAGE 6-100 U (insert Q-register number) U INSERT Q-REGISTER NUMBER COMMAND ================================================================== Insert number into a Q-register FORMAT: nUq m,nUq where n is an integer and q is a Q-register designator. ================================================================== The nUq command stores the integer n in Q-register q (where q is one of the 36 Q-registers). If anything was previously in the numeric part of the Q-register, it is destroyed. m,nUq is equivalent to the nUqm command. That is, this command puts the number n into the numeric storage area of Q-register q and then returns the number m Example: *SLINE 1$0L.U1 This command string will delete the text be- SLINE 2$.U2 ginning at "LINE 1" and preceding "LINE 2". Q1,Q2K$$ Standard TECO PAGE 6-101 ^U (insert text into Q-register) ^U INSERT TEXT INTO Q-REGISTER COMMAND ================================================================== Enter the text following the command into a Q-register. FORMAT: ^Uqtext$ @^Uq/text/ :^Uqtext$ etc n^Uq$ n:^Uq$ where q is a Q-register designator, text is the character string to be inserted into the Q-register, and / is an arbitrary delimiter which is not one the characters in "text". ================================================================== Text is normally placed into a Q-register by copying it from the editing buffer (through the use of the Xq command). The ^U command gives you the option of directly inserting a text into a Q-register. TECO places the text into the Q-register when it begins executing the command string. The command can only be entered directly by using the circumflex construction. :^Uqstring$ appends character string "string" to the text storage area of Q-register "q". n^Uq$ inserts the single character whose 7-bit ASCII code is n into the text storage area of Q-register "q". n:^Uq$ appends the single character whose 7-bit ASCII code is n to the text storage area of Q-register "q". @^Uq/string/, @:^Uq/string/, n@^Uq//, n@:^Uq// are equivalent, respectively, to the ^Uqstring$, :^Uqstring$, n^Uq$, and n:^Uq$ commands, except that alternate delimiters are used and no characters are necessary. Standard TECO PAGE 6-102 V (VERIFY) V VERIFY COMMAND ================================================================== Type out lines of text in the editing buffer. FORMAT: V nV (not in TECO-8) m,nV (not in TECO-8) where n may be positive, negative, or zero. ================================================================== You can type any part of the text in the editing buffer for examination by using the V command. The text TECO types depends on the position of the buffer pointer and the argument(s) given. The V command never moves the buffer pointer. V is always a line-oriented command. The command variations are described in Table 1. Table 1 V Commands Command Argument Function V 1 assumed Type out the current line from the beginning of the line through the next line terminator. Equivalent to 0TT. nV n>0 Type out n-1 lines on either side of the current line. Equivalent to 1-nTnT. [Not in TECO-8.] m,nV m,n>0 Type out m-1 lines before the current lines and n lines after the current line. Equivalent to 1-mTnT. [Not in TECO-8.] Standard TECO PAGE 6-103 ^V (lower-case conversion) ^V LOWER-CASE CONVERSION COMMAND (TECO-10 only) ================================================================== Enable/disable lower-case conversion. FORMAT: ^V 0^V ================================================================== ^V puts TECO into lower case conversion mode. In this mode, all alphabetic characters in string arguments are automatically changed to lower case. This mode can be overridden by explicit case control within the search string. This command makes all strings behave as if they began with a ^V^V. [TECO-10 only] 0^V returns TECO to its original mode. No special case conversion occurs within strings except those case conversions that are explicitly specified by ^V and ^W string build constructs located within the string. [TECO-10 only] Standard TECO PAGE 6-104 W (watch) W WATCH COMMAND ================================================================== Examine or set various Watch attributes. FORMAT: nW n:W m,n:W ================================================================== The W command (scope "WATCH") is present in most implementations of TECO. There are two different variations of the W command. Neither, one, or both may be present. ET flag Bits 9 and 10 indicate which variation(s) are configured and can be used. 1. Video Terminal scope "WATCH" If the VT support is present and your terminal is a video terminal (such as a VT05, VT52, or VT100), ET flag Bit 9 (value 512) will be on. TABLE A: VIDEO TERMINAL WATCH COMMANDS Command Function -1W Refresh the terminal's screen to show the contents of the text buffer. -nW Tell the video terminal screen refresher that the top n-1 lines of the screen have been altered. The screen refresher will completely redraw the top n-1 lines of the screen upon the next -1W command. nW Place the default cursor line at line n of the VT52's screen. The initial default cursor line is line 16. This command makes the window support forget the screen image and any special associated modes (SEEALL, MARK, HOLD). 0W Forget screen image, SEEALL mode, mark, hold mode, scrolling, and set cursor line to default (2/3 of the way down the screen) W Do scrolling update if scrolling; else nop. 32768W Forget that output was done. Normally, if the user outputs to the terminal with a command such as T, n^T, or ^A, TECO will believe that the window needs updating, and upon the next -1W command, TECO will refresh the entire window display. Issuing the 32768W command informs TECO that the output command did not destroy the window. [TECO-11 only] Standard TECO Page 6-105 W (cont) The :W command is used to interrogate and set video terminal status information, as well as implement some of the more advanced features of the video terminal "WATCH" functions. TABLE B: VIDEO TERMINAL STATUS COMMANDS Command Function 0:W Return a number representing the type of scope in use as the editing terminal. Current values are: 0 VT52 1 VT61 [TECO-10 only] 2 VT100 in VT52 mode 4 VT100 in ANSI mode 6 VT05 :W Equivalent to 0:W 1:W Return the horizontal size of the user's editing scope. This number represents the number of character positions available horizontally along the face of the scope. 2:W Return the vertical size of the user's editing scope. This number represents the number of lines of text that can appear on the screen of the terminal. 3:W Returns SEEALL mode. 0 represents off and -1 represents on. In SEEALL mode, a visible indication is shown in the window for every character, including characters that normally don't print. 4:W Returns mark status of window support. 0 means that no mark has been set. A value of n means that a mark has been set at window position n-1. This status is used by software that uses the window support and by the support itself in the case of scopes that support reverse video. 5:W Returns the hold mode indicator. 0 means off, -1 means hold whole screen, and a positive value, n, means hold all but top and bottom n lines. If hold mode is on, then scrolling is inhibited until the cursor is about to run off either end of the screen. This makes the window display more palatable on terminals on a slow line. If hold mode is on, the window support will scroll the window as necessary in an attempt to keep the cursor centered. 6:W Returns buffer pointer position of character that was in the upper left hand corner of the window as of the last -1W command. Standard TECO Page 6-106 W (cont) 7:w Returns the number of scrolling lines. If n is zero, then scrolling is turned off. Consult the appendices for details. -256+n:W inserts characters at "dot" until... characters are read (echo off) from the terminal and inserted at "dot" until and according to the microcoded bits in n 128 => return immediately if no characters 64 => return on any character 32 => don't update screen (i.e., don't do a -1W) 2 => return on TAB's 1 => no need to initially refresh the screen return is always done on control characters (0 through 37 and 177 except TAB) returned value has return character code in low byte (0 through 177 or 377 for returned immediately); sign bit (value 32768) is set if one or more inserts were done the screen is only updated if 32 is not in n and there is no typeahead to process; if 128 in n is not set then the update will occur after all typeahead insert(s) are done n,:W same as n,0:W n,0:W sets scope type (n must be 0, 2, 4, or 6) n,1:W sets scope width (n must be between 10 and 254 and even) n,2:W sets scope height (n must be between 10 and 127) n,3:W sets SEEALL mode (n=0 for off, n<>0 for on) n,4:W sets mark (n=0 for none, n<>0 for mark @ n-1) n,5:W sets hold mode (n=0 for off, n=-1 for hold whole screen, n>0 for hold all but top and bottom n lines) n,6:W sets position for upper left hand corner for next -1W (n=0 for default cursor positioning, n<>0 for upper left hand corner @ n-1) (applies only if hold mode is on and cursor is within the specified limits) n,7:W sets number of scrolling lines (n=0 for no scrolling, n<>0 for scroll bottom n lines, where n must be greater than 1 and scope height minus n must be greater then 9) same operation as -256+n:W except if m typeahead insert(s) are done the screen will be updated (provided 32 is not set in n) Standard TECO Page 6-107 W (cont) Notes on Hold Screen mode (5:W) If "hold whole screen" mode (-1,5:W) is set, the hardware scrolling of the scope will never be used. This allows a program to set hold whole screen mode (-1,5:W) and, then, shorten the scope's height (n,2:W) without problems. The bottom 'unused' lines of the scope will never be altered by TECO and can be used by the program for other purposes. Notes on Scrolling (7:W) Whenever a scrolling lines modification is issued (n,7:W), TECO alters the scope's height (2:W) accordingly. For example, if 2:W is currently returning a value of 24, then, after a 5,7:W command, 2:W will return a value of 19. Doing a 0,7:W will restore 2:W to returning 24. 2. Refresh scope "WATCH" If refresh scope support is present and a refresh scope is available (such as a VS60 or a VR12), bit value 1024 of the ET flag will be on. TABLE C: REFRESH SCOPE WATCH COMMANDS Command Function W Update the refresh scope screen to reflect the contents of the text buffer surrounding the text pointer ("dot"). 0W Turn off the refresh scope display. nW Set the number of lines to be displayed around the text pointer to n. Standard TECO PAGE 6-108 ^W (upper-case conversion) ^W UPPER-CASE CONVERSION COMMAND (TECO-10 only) ================================================================== Enable/disable upper-case conversion. FORMAT: ^W 0^W ================================================================== ^W puts TECO into upper case conversion mode. In this mode, all alphabetic characters in string arguments are automatically changed to upper case. This mode can be overridden by explicit case control within the search string. This command makes all strings behave as if they began with a ^W^W. [TECO-10 only] 0^W returns TECO to its original mode. No special case conversion occurs within strings except those case conversions that are explicitly specified by ^V and ^W string build constructs located within the string. [TECO-10 only] Standard TECO PAGE 6-109 X (eXtract) X EXTRACT COMMAND ================================================================== Insert text into a Q-register FORMAT: nXq m,nXq n:Xq where n is positive, negative, or zero if there is one argument. If there are two arguments, m0 Copies everything from the current buffer pointer postion through the nth following line terminator character into Q-register q. Xq 1 is assumed Copies the text of the current line from the buffer pointer position to the next line terminator into Q-register q. 0Xq 0 Copies the text of the current line preceding the buffer pointer to the buffer pointer into Q-register q. -nXq -n<0 Copies everything from the current buffer pointer position back through the beginning of the line containing the nth preceding line terminator into Q-register q. -Xq -1 is assumed Copies the text of the line preceding the current line and the current line to the buffer pointer position into Q-register q. Standard TECO PAGE 6-110 X (cont.) m,nXq m where n is the number of pages to be ignored. The Y command aborts if the text buffer is not empty and an output file is open. Examples: *ERREPORT.TE$Y$$ This command string opens the file REPORT.TE for input and reads in the first page of that file. *ERDTA3:DATA.FOR$YYY$$ This command string reads in and discards the first two pages of the DECtape file DATA.FOR, and then reads in the third page of that file. If an output file were open, you would have to type 3. Standard TECO PAGE 6-114 ^Y (span last string) ^Y SPAN LAST STRING COMMAND (TECO-11 only) ================================================================== Span the text just searched for or inserted. FORMAT: ^Y ================================================================== ^Y (caret/Y) is equivalent to ".+^S,.", the n,m numeric argument spanning the text just searched for or inserted. This value may be used to recover from inserting a string in the wrong place. Type "^YXAFR$" to store the string in Q-register A and remove it from the buffer. You can then position the pointer to the right place and type "GA" to insert the string. [TECO-11 only] Standard TECO PAGE 6-115 Z (end of buffer) Z POSITION INDICATOR ================================================================== Indicates the last position in the editing buffer. FORMAT: Z ================================================================== Z is a buffer position indicator that equals the number of characters in the buffer. Thus, Z is a number that is the count of how many characters are in the buffer. While Z is often used as an argument to a command, you can also use it in arithmetic expressions. Example: One common use of Z is to verify if characters have been read into the editing buffer, e.g., the command string segment ...ZU1 A Z-Q1"E... stores a number which is the count of the characters in the buffer, and appends a new page. The second Z indicates the new number of characters in the buffer. When the former count is subtracted from it, if that number equals zero, then no characters were read in. Standard TECO PAGE 6-116 ! (tags) !tag! ================================================================== A string of ASCII characters used to identify a location in a command string. FORMAT: !tag! where ! precedes and follows the ASCII string. ================================================================== When an O command directs the execution of a command string from the its linear order of execution, the place to which TECO is directed is called a tag. The tag is delimited both before and after with exclamation points. Tags may be thought of in much the same way as labels in other programming languages. The length limitation of a tag is solely that of what will fit in the command string register. Because you do not have to reference tags, they can serve as comments within a command string or macro. (Normally, comments are included only in lengthly TECO macros that will be maintained.) Standard TECO PAGE 6-117 " " BRANCHING COMMANDS ================================================================== Depending upon the argument, skip any command that precedes an apostrophe at the same nesting level. FORMAT: n"X....' where n is the argument to the conditional execution command; " signals that the command is a conditional execution command; X is the condition to matched; and the ' represents the place to begin execution if the condition is not satisfied. ================================================================== In this command, n is the numeric argument on which TECO bases its decision to execute a command string. The quotation mark (") is the first character of all conditional execution commands. Immediately following the " is a character which must be one of those listed in Table 1. Terminate this command string with an apostrophe ('). If n satisfies the condition, TECO executes all the commands until the ' in the usual manner. If there is no branch command within the range "...', then after TECO executes the last command in the range, command execution falls through the apostrophe and execution begins with the next command following it. If n does not satisfy the condition, then TECO skips all the commands before the apostrophe, and command execution continues with the first command following the apostrophe. Only use the " and ' in matching pairs. You may nest them in the same manner that parentheses surrounding arithmetic expressions can be nested. As TECO scans for the matching single quote, it keeps an iteration count for each level of nested iteration which it finds. TECO then ignores any single quotes which occur at a nesting level greater than 0. NOTE All conditionals must end at the same macro level in which they begin. The individual conditional execution commands are shown in table 1. Standard TECO PAGE 6-118 " (cont.) Table 1 Conditional Execution Commands Command Function n"A Execute the following command string if n equals the ASCII code for an alphabetic character (upper or lower case A to Z). n"C Execute the commands that follow if n is an ASCII character (A-Z, a-z, 0-9). n"D Execute the following command string if n equals the ASCII code for a digit (0 to 9). n"E Execute the commands that follow if n=0. n"F Execute the commands that follow if n represents a false (flag is off)(i.e., if n=0). n"G Execute the commands that follow if n>0. n"L Execute the commands that follow if n<0. n"N Execute the commands that follow if not = 0. n"R Execute the commands that follow if n is the ASCII code for an alphanumeric character (A-Z, a-z, 0-9). n"S Execute the commands that follow if n represents success (i.e., if n<0). n"T Execute the commands that follow if n represents true (flag is on) (i.e., if n<0). n"U Execute the commands that follow if n represents unsuccessful (i.e., if n=0). n"V Execute the following command string if n equals the ASCII code for a lower case alphabetic character (lower case A to Z). [Not in TECO-8] n"W Execute the following command string if n equals the ASCII code for an upper case alphabetic character (upper case A to Z). [Not in TECO-8] n"< Execute the commands that follow if n<0. Same as n"G. n"> Execute the commands that follow if n>0. Same as n"L. n"= Execute the commands that follow if n=0. Same as n"E. Standard TECO PAGE 6-119 " (cont.) Examples: *!START!JPDP-8 TECO $ !INSERT PAGE HEADING! !CHANGE 5K TO 6K! !CHANGE WAR TO LOVE! PZ"NOSTART$ !GET NEXT PAGE AND! 'EF$$ !RESTART IF NOT NULL! This small editing program also contains an example of the O unconditional branching command, i.e., the OSTART$ command which causes a jump back to !START!. String tags are also used purely for documentation, e.g., !INSERT PAGE HEADING!. This example also shows how a conditional execution command may be combined with an O command to produce a conditional branch. 1. After TECO performs all three of the editing functions on the page, it executes the P command to write this page and read in the next. 2. The program then tests Z (the number of characters in the buffer) to determine if any data was read in. 3. If Z does not equal 0, data was read in; therefore a branch is taken to restart the program. 4. When Z=0, the command OSTART$ is skipped, and execution branches to the concluding EF command. This technique fails when a file contains null pages (consecutive form feed characters). The ^N end-of-file test may be preferred. *YZ"N!##! Z-4000+1"G4000J 0L 12I$ 0,.P0,.K 0##$ 'ZJ A .-Z"NO##$ ' 'PEF$$ * This slightly more complex command string shows how conditional execution commands may be nested. If the first Y command produces no data, the "N command sends execution to the matching apostrophe on the right. This is the last apostrophe, immediately prior to the PEF. Otherewise, TECO executesthe commands following the "N. The function of this command string is to convert a file with pages of arbitrary lengths to one with pages of approximately 4000 characters each. Standard TECO PAGE 6-120 " (cont.) The command string operates as follows: 1. Z-4000+1"G means if Z>4000, i.e., there are at least 4000 characters on the current page, execute the following commands; otherwise, skip to the matching apostrophe (between $ and Z). 2. If Z>4000, 4000J and 0L moves the pointr to the end of the last complete line before the 4000th character in the buffer. 3. Then, 12I$ and 0,.P outputs this much of the buffer with a form feed character after it, and 0,.K deletes that which has been output. 4. Now, go back to !##! and test Z again. Stay in this loop until Z<4000. 5. Execution then skips to the apostrophe. ZJ moves the pointer to the end of the current buffer. 6. A appends another page., but leaves the pointer (.) at the end of the previous page 7. .-Z"N checks to determine if any data was actually read in. If so, the loop is reentered at !##!; otherwise the end of the file has been reached. 8. When .-Z=0, execution skips to the matching apostrophe and then falls through the next apostrophe to the PEF that closes the output file. NOTE: Another algorithm would be Y EC$$ *$$ This example shows how the value returned by a colon search can be used as the argument for a conditional execution command. 1. The N command searches through the file for the first occurrence of SIN on any page. 2. When SIN is found, the command :SCOS$ checks for an occurrence of COS following SIN on the same page. 3. The colon search command returns the value -1 if the search is successful, and 0 if there is no COS following SIN on the page. 4. This value is then used as the numeric argument for the "S command. Standard TECO PAGE 6-121 " (cont.) 5. If :SCOS$ has a value of -1, the occurrence of COS that was found is replaced by TAN. 6. If :SCOS$ has a value of 0, the commands -3DITAN$ are skipped. 7. We then jump to the end of this page, ignoring all further occurences of SIN and COS on it, and continue the iteration process. Standard TECO PAGE 6-122 % (change number in Q-register) % CHANGE NUMBER IN Q-REGISTER COMMAND ================================================================== Change the number stored in a Q-register by n. FORMAT: n%q where n is a number and q is a Q-register designator. ================================================================== The command n%q adds n to the integer in Q-register q and then returns the new value in the same manner as a Qq command. If you omit n, 1 is assumed (i.e., 1%q). Note that this command returns a value as well as incrementing the stored value. If you wish to increment the value in the Q-register, but do not want the returned value to be used as an argument for the next command, type an ESCAPE after the n%q command, (that is, n%q$). Standard TECO PAGE 6-123 . (position indicator) . POSITION INDICATOR ================================================================== Return a number equal to the number of characters preceding the buffer pointer in the editing buffer. FORMAT: . ================================================================== A period equals the number of characters to the left of the current positon of the buffer pointer, and hence represents the buffer pointer position itself. That is, it represents the number of characters from the beginning of the buffer to the present buffer pointer position. The . can be used in arithmetic expressions. Standard TECO PAGE 6-124 : (modifier) : MODIFIER ================================================================== 1. Return a value if a search fails. FORMAT: :nStext$ :n@S/text/ where S represents any search command and / is an arbitrary delimiter which is not one of the characters in "text". 2. Do not output a carriage return after typing out a number. FORMAT: := :== 3. Cause a Gq command to type-out its contents without inserting the contents into buffer. FORMAT: :Gq where q is a Q-register designator. 4. Append to existing contents of buffer, e.g. n:Xq ================================================================== 1. : S MODIFIER Use the colon modifier to alter the execution of a serach command in the event a search fails. Normally, a search that fails causes TECO to print an error message; if you use the colon modifier, no error message is printed. Instead, every colon search returns a numeric value that TECO can print out, store in a Q-register, or test by a conditional branch. A colon search command returns the value -1 if the search is successful, and the value 0 if the search fails. The general form of a colon search command is the same for S, FS, N, and FN searches: nSstring$ The colon normally precedes the search command letter and its numeric argument, if any. Both the colon and @ modifier may be used on a search command in either order. Standard TECO PAGE 6-125 : (cont) Just as the Z command takes on a value that may be used as a numeric argument, so also the command :Sstring$ takes on a value of 0 or -1 after TECO executes the search. If this is the last command in a command string, or if the command following it does not take a numeric argument, the value returned by the colon is discarded. Consequently, a colon search should be followed by a command that takes a numeric argument. The colon search commands reposition the buffer pointer in the same manner as other search commands, regardless of whether or not the returned value is used. The primary use of the colon search is in programmed editing. The command is usually followed by a conditional command. 2. : NUMERICAL TYPE-OUT MODIFIER See the = and == discussion for information on how : modifies numeric type-out commands. 3. : Q-REGISTER TYPE-OUT COMMAND See the G command for information. 4. : Q-REGISTER APPEND COMMAND See the X command for information. Standard TECO PAGE 6-126 ; (exit from loop) ; CONDITIONAL EXIT FROM LOOP COMMAND ================================================================== 1. If an argument is positive or zero, jump out of current iteration field. FORMAT: n; where n is a number, either explicit or returned. 2. If the search command immediately preceding the ; failed, jump out of current iteration field. FORMAT: ; 3. If the search command immediately preceding the ; succeeded, jump out of current iteration field. FORMAT: :; ================================================================== Terminate repetition of a command string loop before the iteration count is satisfied by using the conditonal iteration exit command, semicolon (;). You can only use the ; command within angle brackets. You may use it with or without a numeric argument. When you use a semicolon without a numeric argument, it evaluates the outcome of the last search (of any kind) that was executed before TECO encountered the semicolon. If this search was successful, command execution continues within the loop, as if no ; were present. If, however, the most recent search failed, the ; command causes all those commands that follow the ; in the loop to be skipped over, and command execution to pass to the first command following the right angle bracket which closes the innermost loop which contains the semicolon. The semicolon command is most often used with a numeric argument. TECO ignores the command n; if n<0. However, if n>0 or n=0, the command n; causes command execution to exit from the loop just as a ; command exits from the loop when a search fails. Standard TECO PAGE 6-127 <...> (loop) <...> LOOP COMMAND ================================================================== Continue executing the command string until conditions are met. FORMAT: n<...> where n is a positive number. If n is omitted, the command is executed an infinite amount of times or until an exit condition within the loop occurs. ================================================================== You can cause a group of commands to be iterated (repeatedly executed) any number of times by placing the commands within angle brackets. The left angle bracket marks the beginning of a command string loop and the right angle bracket marks the end of the loop. These command string loops can be nested in the same manner as arithmetic expressions are nested within parentheses. Loops should be nested to no more than approximately 10 levels; otherwise, a pushdown list overflow may occur. You may use a numeric argument to type the number of times a given loop is executed. The argument is placed before the left angle bracket in the form n<...>. This causes the group of commands within the brackets to be iterated n times. In a command of the form <...>, if the argument is less than or equal to zero, TECO skips the commands within the angle brackets. If no argument is given, the number of iterations is assumed to be infinite. Example: *J8<$L>$$ This command string inserts a tab at the beginning of the first eight lines in the buffer and leaves the pointer positioned at the beginning of the ninth line. The J command starts the pointer off at the beginning of the first line. The first command in the loop, $, inserts a tab. Then the L command moves the pointer to the next line to prepare for the next iteration of the loop. Standard TECO PAGE 6-128 <...> (cont.) *J<0LIJAN$ This command string inserts JAN at the begin- FS1969$1970$;> ning of the first line in the buffer and at HT$$ the beginning fo each line that contains JAN REPORT 1970. It also changes the 69 in every occur- DEPT: rence of 1969 to 1970. The action is as the JAN 1970 SALES J command starts the operation at the WHOLESALE beginning of the buffer. The first execution RETAIL of the 0L does nothing. IJAN$ then inserts JAN 1970 EXPENSES JAN at the beginning of the first line. Now OVERHEAD a search is made for 1969. When it is found, ADVERTISING FS1969$1970$ changes 1969 to 1970. This com- JAN 1970 RETURNS pletes the first iteration; execution loops JAN 1970 INVENTORY the first iteration; execution loops back to the <. 0L moves the pointer to the beginning of the line where the 1969 was found. Here JAN is inserted and then a search is begun for the next 1969. This continues until the search comand fails to find another 1969. When the search fails, the pointer is moved to the beginning of the buffer. HT is the next command which is executed. (This macro assumes that no line contains more than one 1969.) *EBfilespec$50000EX$$ This removes all form feeds from a file. *$$ This command causes a search of the current page for all occurrences of the string READ and replacement of them with the string WRITE. *<@FN/ERROR//;>$$ This command causes TECO to search all of the following pages for the string ERROR and delete every occurrence of it. The @ construction must be used in this case because it allows you to specify a delimiter other than $. The delimiter must be specified twice after the string; the first to delimit the string and the second to indicate that a replacement string is not present. If $ were used as the delimiter, a double $ would be present which would cause an erroneous termination of the command string. Standard TECO PAGE 6-129 = (numerical type out) = NUMERICAL TYPE-OUT COMMAND ================================================================== Type-out a number in decimal, octal or (TECO-11 only) hexadecimal (with or without a following carriage return) FORMAT: = := == :== === (TECO-11 only) :=== (TECO-11 only) where a single = means type out in decimal, a double = means type out in octal, a triple = means type out in hexadecimal, and the : modifier means do not type a carriage return after typing. ================================================================== Table 1 = Commands Command Function n= Type the value of n in decimal followed by a carriage return/line feed. n:= Same as n= except the carriage return/line feed is suppressed. n== Type the value of n as an unsigned octal number followed by a carriage return/line feed. n:== Same as n== except the carriage return/line feed is suppressed. n=== Type the value of n in hexadecimal followed by a carriage return/line feed. n:=== Same as n=== except the carriage return/line feed is suppressed. Examples: *YZ==$$ This reads in a page and then types out the (deci- 2529 mal) number of characters in the page. *0A==$$ This types the octal representation of the next 40 character in the buffer. *YNCHAPTER $\=$$ This command searches for the next chapter heading 16 and then types out the number of the chapter. The buffer pointer points to the location immediately following the 6. Standard TECO PAGE 6-130 ? (trace) ? TRACE COMMAND ================================================================== Trace the execution of a TECO command string FORMAT: ? where ? is inserted into the command string. ================================================================== The use of a question mark causes TECO to enter trace mode. In trace mode, TECO types out each command as it is executed. A second question mark takes TECO out of trace mode. The ? command only traces commands that TECO executes, i.e., if a branching command causes a command to be skipped over, TECO does not print the commands skipped over. Example: *JHT? !L!1A-9"N !M!1A-58"NCOM$ 'CD$ 'LOL$$ AB: LINE 1 LINE 2 C: LINE 3 LINE 4 !L!1A-9"N!M!1A-58"NCOM$1A-58"NCO!M!1A-58 "NCD $'LOL$1A-9"NLO!L!1A-9"N!M!1A-58" NCO!M!1A-58"NCD $'LO!L!1A-9"NLO!L!1A-9!M !1A-58"NC?POP *J?HT$$ J? AB: LINE 1 After the first question mark command, TECO LINE 2 begins typing out each command as it is exe- C: LINE 3 cuted. This enables you to see exactly what LINE 4 the command string is doing. The ?POP error message is caused by the attempt to move the pointer beyond the end of the fourth (and last) line with the C command. The second question mark command turns off trace feature so that the HT following it is not printed. Standard TECO PAGE 6-131 @ (text delimiter modifier) @ TEXT DELIMITER MODIFIER ================================================================== Modifies the next command which takes a text argument to use the delimiter form. FORMAT: @x/text/ where x is one of the commands that takes a text argument and / is an arbitrary delimiter which is not one of the characters in "text". ================================================================== You use an @ modifier to alter the method by which TECO reads a command's text. The general form and some of the commands for which the @ modifier is applicable are listed in Table 1. Table 1 @ Commands @nS/text/ Search page @nN/text/ Search file @nFS/text1/text2/ Search page and replace @nFS/text1// Search page and delete @I/text/ Insert text n@I// Insert character @EB/filespec/ Edit Backup @EG/text/ Exist and execute text @ER/filespec/ Edit read @^Uq/text/ Insert text in Q-register Place the @ modifier before the command and before a numeric argument, if any. When you use the @ modifier, the text string is delimited not by the command and an ESCAPE, but by the first character you type after the command and the next recurrence of this command. In the above examples, the delimiting character is a slash. The delimiting character may be any character except a character that appears in the text itself. Using the @ modifier, you may enter single (but not double) ESCAPEs into a text string. Use the @ modifier in the above commands to separate the strings with a delimiting character other than an ESCAPE. This is useful in cases where a double ESCAPE cannot terminate the command. For example, if you are searching for a string, then deleting it without replacement, you would ordinarily type a double after an FS or FN command. However, if this were within a command string, the command would be terminated at this point unless you used an @ modifier. Standard TECO PAGE 6-132 [ (push Q-register) [ PUSH Q-REGISTER COMMAND (Not in TECO-8) ================================================================== Push a Q-register onto the Q-register push-down list. FORMAT: [q Where q is any valid Q-register. ================================================================== [q copys the contents of the numeric and text storage areas of Q-register q into the Q-register push-down list. This command does not alter either the numeric or text storage areas of Q-register q. It does not use numeric values. Numeric values are passed through this command as if it did not occur, allowing macros to save temporary Q-registers and still accept numeric values. The command sequence [A]B copies the text and numeric value from Q-register A to Q-register B. [Not in TECO-8] Standard TECO PAGE 6-133 \ (convert a number) \ CONVERT A NUMBER COMMAND ================================================================== 1. Returns the numbers following the buffer pointer. FORMAT: \ 2. Insert a character numeric string into the buffer. FORMAT: n\ where n is the number to be inserted. ================================================================== 1. \ COMMAND The command (without a numeric argument) is equivalent to the value of the digit string (optionally preceded by a + or - sign) immediately following the current position of the buffer pointer. The value is terminated by the first character TECO encounters that is not a legal digit in the current radix. If there is no digit, TECO returns a 0. TECO interprets the digit string in the current radix. Example: *YNCHAPTER $\=$$ This command searches for the next chapter 16 heading and then types out the number of the chapter. The buffer pointer is positioned immediately following the 6 after thiscommand has been executed. 2. n\ INSERTION COMMAND You use the n\ command to insert the ASCII representation of a number n into the buffer. TECO inserts the number in the current radix. For example, 349\ inserts the ASCII characters, 3, 4, and 9 into the buffer immediately preceding the pointer. Note that n does not have to be a number typed in by the user. It can be a value which some other TECO command returns. Standard TECO PAGE 6-134 ] (pop Q-register) ] POP Q-REGISTER COMMAND (Not in TECO-8) ================================================================== Pop a Q-register from the Q-register push-down list. FORMAT: ]q :]q Where q is any valid Q-register. ================================================================== ]q pops from the Q-register push-down list into Q-register q. Any previous contents of Q-register q are destroyed. Both the numeric and text parts of the Q-register are loaded by this command. The Q-register push-down list is a last-in first-out (LIFO) storage area. This command does not use numeric values. Numeric values are passed through this command as if it did not occur. This allows macros to restore Q-registers and still return numeric values. [Not in TECO-8] :]q executes the ]q command and return a numeric value. A -1 indicates that there was another item on the Q-register push-down list to be popped. A 0 indicates that the Q-register push-down list was empty, so Q-register q was not modified. [Not in TECO-8] Standard TECO PAGE 6-135 ^^ (ASCII value of character) ^^x ASCII VALUE OF ASCII CHARACTER COMMAND ================================================================== Return the ASCII value of a character FORMAT: ^^x where x is an ASCII character ================================================================== The ^^ command, when followed by an arbitrary character x, is equivalent to the ASCII value of that character. For example, in the command ^^A, the character A is an argument for ^^ and TECO does not interpret it as a command. Examples: *^^MU0$$ This command stores the ASCII value of the letter M (77) into Q-register 0. Standard TECO PAGE 6-136 _ _ COMMAND ================================================================== Search for a character string and discard all pages before the string is found FORMAT: n_text$ n@_/text/ which n indicates what occurence of the string is to be found and / is an arbitrary delimiter which is not one of the characters in "text". ================================================================== The backarrow command is identical to the N command except that a _ search generates no output. Generally, where the N command executes a P, the _ executes a Y. You use the _ search for examination functions and for discarding parts of a file. You can also use the _ command with a single numeric argument. The command n_ causes a search for the nth occurrence of the search string. When you omit n, TECO assumes n=1. n must always be greater than 0. "text" may include the match control characters described in Chapter V. The _ command may use a : modifier. Example: *5_VERSION88$$ This command can be used to determine if the string VERSION88 occurs in the input file five times. If it does, the pointer is positioned immediately after the fifth occurrence, and everything in the input file preceding the page on which the fifth occurrence is located, is discarded. If it is not, the entire file is is discarded. Standard TECO PAGE 7-1 Error Messages CHAPTER VII ERROR MESSAGE PROCESSING 7.1 ERROR MESSAGES When TECO encounters an illegal command or a command that cannot be executed, an error message is printed at the terminal. Error messages are of the form: ?XXX Message where "XXX" is an error code and "Message" is an explanatory message. When an error message is generated, the command to which it refers is not executed, the rest of the current command string is ignored, and TECO prints an asterisk at the left margin to indicate that it is ready to accept further commands. In some cases it may be difficult to determine which command in a long command string resulted in an error message. Typing a question mark immediately after the TECO-generated error message causes TECO to print the current command string up to and including the erroneous character. When used in this manner, the question mark must be the first character typed after the error message is printed. It is not necessary to follow the question mark with an ESCAPE. Some error messages include the mention of a specific character in error (or sometimes a string of characters in error). In such cases, the character in error is printed in a special format if it is not a printing character, so that you will be best able to see the error of your ways. If the character is a control character, , it will be displayed as , except for a few special control characters that will be displayed as shown in the following table: Character ASCII Special display 11 12 13 14 15 33 In addition, TECO-8 displays special symbols to represent the presence of match control constructs within a search string. These are shown below: Display Construct Meaning ^N Match anything except next construct ^X Match any character Standard TECO PAGE 7-2 Error Messages ^S Match any separator 7.2 IMPLEMENTATION-SPECIFIC ERROR MESSAGES If you are merely interested in the general flavor of TECO's error messages, or want to look up the meaning of a specific error message, consult APPENDIX B. In that appendix, all TECO error messages are listed alphabetically by their 3-letter code. This 3-letter code is, in general, the same across all TECO implementations. Whereas appendix B merely paraphrases the wording on the error messages, the following paragraphs give you the exact wording of all the error messages for all TECO implementations covered by this manual. The 3-letter code of the error message is given first, then the one-line error message (produced if EH&3=2) is given, then the detailed error message (produced if EH&3=3) is given. 7.2.1 TECO-11 ERROR MESSAGES Code Message ?BNI > not in iteration ?CPQ Can't pop Q-reg ?DTB Delete too big ?FNF No such file "filespec" ?IEC Illegal E character ?IFC Illegal F character ?IIA Illegal insert arg ?ILL Illegal command ?ILN Illegal number ?IPA Illegal P arg ?IQC Illegal " character ?IQN Illegal Q-reg name ?IRA Illegal radix arg ?ISA Illegal search arg ?ISS Illegal search string ?IUC Illegal ^ character ?MEM Memory overflow ?MRP Missing ) ?NAB No arg before ^_ ?NAC No arg before , ?NAE No arg before = ?NAP No arg before ) ?NAQ No arg before " ?NAS No arg before ; ?NAU No arg before U ?NFI No file for input ?NFO No file for output ?NYA Numeric arg with Y ?OFO Output file already open ?PDO Push-down list overflow ?POP Pointer off page ?SNI ; not in iteration Standard TECO PAGE 7-3 Error Messages ?SRH Search failure "string" ?STL String too long ?UTC Unterminated command ?UTM Unterminated macro ?XAB Execution aborted ?YCA Y command aborted RT-11 ERROR MESSAGES ?DEV Invalid device ?DIO Directory I/O error ?INP Input error ?MFN Missing file name ?NRO No room for output ?OUT Output error ?UEA EA not implemented ?UEI Edit indirect not implemented ?UEN EN not implemented ?UEP EP not implemented RSTS/E ERROR MESSAGES ?ERR RSX-11 ERROR MESSAGES (includes VAX/VMS) ?nnn Standard TECO PAGE 7-4 Error Messages 7.2.2 TECO-10 ERROR MESSAGES ?ARG Improper Arguments The following argument combinations are illegal: 1) , (no argument before comma) 2) M,N, (where M and N are numeric terms) 3) H, (because H=B,Z is already two arguments) 4) ,H (H following other arguments) ?ASN Ambiguous Switch Name: "/SWITCH" The switch "/SWITCH" is not uniquely abbreviated, i.e. more than one switch will match "/SWITCH". A longer, unique form of the switch should be used. ?BAK Cannot Delete Old Backup File Failure in RENAME process at close of editing job initiated by an EB command or a TECO command. There exists an old backup file "filnam.BAK" with a protection "" such that it cannot be deleted. Hence the input file "filespec" cannot be renamed to "filnam.BAK". The output file is closed with the filename "Filespec". The RENAME MUUO error code is "nn". ?BNF Block not found This is an internal error and should be reported. A block of text, such as a previously-executed command, or q-register text, was not in the linked list of such blocks. ?BPT Breakpoint in macro "q" The most recent EB file was: "filespec" The most recent ER file was: "filespec" The most recent EW file was: "filespec" The most recent search argument was: "string" EO="nn", ET="nn", ED="nn" ARG="nn", SARG="nn", VALUE="nn", Flags="nn" ?CCM CCL Command Missing TECO-10 was run with a run-offset of one (1) and there was no file 'EDT' in TMPCOR or ' EDT.TMP' on the user's disk area. Standard TECO PAGE 7-5 Error Messages ?CEF Core expansion failure The current operation requires more memory storage than TECO-10 now has and TECO-10 is unable to obtain more core from the monitor. This message can occur as a result of any one of the following things: 1) Command buffer overflow while a long command is being typed, 2) Q-register buffer overflow caused by an X or [ command. 3) Too many Q-registers in use (.gt.5000), 4) Too much nesting or recursion of the M command. 5) Editing buffer overflow caused by an insert command or a read command or other causes. ?CFP Can't Find Overflowed PDL A PDL overflow trap occurred, but TECO-10 could not find the PDL that caused the overflow. This is an internal error and should be reported, along with a teletype printout showing what the user was doing. ?CON Confused use of conditionals Conditionals, parenthesized arguments, and iterations must be properly nested. The user probably used some construct like: N"E...(...' where an iteration or parenthesized argument is begun in a conditional but not terminated in the same conditional. ?EBD EB with Device "dev:" is Illegal The EB command and the TECO command may be specified only with file structured devices (ie: disk and DECtape.) ?EBF EB with Illegal File "filespec" The EB command and the TECO command may not be used with a file having the filename extension ".BAK" or a file having the name "NNNXTC.TMP" where NNN is the user's job number. The user must either use an ER-EW sequence or rename the file. ?EBO EW Before Current EB Closed An ER or EW command may not be given while an EB command is in progress. Give an EF to close the files if you wish to do an ER or EW, or an EK to cancel the current EB. ?EBP EB Illegal because of file "filespec" Protection The file "filespec" cannot be edited with an EB command or a TECO command because it has a protection "" such that it cannot be renamed at close time. ?EMA EM with Illegal Argument The argument N in an NEM command must be greater than zero. Standard TECO PAGE 7-6 Error Messages ?EMD EM with no Input Device Open EM commands apply only to the input device, and should be preceded by an ER (or equivalent) command. To position a tape for output, that unit should be temporarily opened for input while doing the EM commands. ?END EN with a Device is Illegal Since it is not possible to RENAME across devices. There must be no device specified in an EN command. The device is specified in the ER command which selected the file. ?ENO EN REQUIRES AN OPEN INPUT FILE EN commands apply to the file currently open for input. You must execute an ER command to select the file to be RENAME'd or deleted before executing an EN. ?ENT-00 Illegal Output Filename "filespec" ENTER UUO failure 0. The filename "filespec" specified for the output file cannot be used. the format is invalid. ?ENT-01 Output UFD for the file "filespec" not found ENTER UUO failure 1. The file "filespec" specified for output by an EE, EW, EA, EZ, OR MAKE command cannot be created because there is no user file directory with the project-programmer number "[p,pn]" on device "dev:". ?ENT-02 Output Protection Failure ENTER UUO failure 2. The file "filespec" specified for output by an EE, EA, EZ, EB, MAKE, or TECO command cannot be created either because it already exists and is write-protected against the user, or because the UFD it is to be entered into is write- protected against the user. ?ENT-03 Output File being Modified ENTER UUO failure 3. The file "filespec" specified for output by an EE, EW, EA, EZ, EB, or TECO command cannot be created because it is currently being created or modified by another job. ?ENT-06 Output UFD or RIB Error ENTER UUO failure 6. The output file "filespec" cannot be created because a bad directory block was encountered by the monitor while the ENTER was in progress. The user may try repeating the EE, EW, EA, EB, or TECO COMMAND, BUT IF The ERROR PERSISTS, IT IS IMPOSSIBLE TO PROCEED. Notify your system manager. Standard TECO PAGE 7-7 Error Messages ?ENT-14 No Room or Quota Exceeded on "dev:" ENTER UUO FAILURE 14. The output file "filespec" cannot be created because there is no more free space on device "dev:" or because the user's quota is already exceeded there. ?ENT-15 Write Lock on "dev:" ENTER UUO failure 15. The output file "filespec" cannot be created because the output file structure is write-locked. ?ENT-16 Monitor Table Space Exhausted ENTER UUO failure 16. The output file "filespec" cannot be created because there is not enough table space left in the monitor to allow the enter. The user may try repeating the EE, EW, EA, EB, or TECO command, but if the error persists he or she will have to wait till conditions improve. ?ENT-23 Output SFD Not Found ENTER UUO failure 23. The output file "filespec" cannot be created because the Sub-File-Directory on which it should be entered cannot be found. ?ENT-24 Search List Empty ENTER UUO failure 24. The output file "filespec" cannot be created because the user's file structure search list is empty. ?ENT-25 Output SFD Nested Too Deeply ENTER UUO failure 25. The output file "filespec" cannot be created because the specified SFD path for the ENTER is nested too deeply. ?ENT-26 No Create for Specified SFD Path ENTER UUO failure 26. The output file "filespec" cannot be created because the specified sfd path for the ENTER is set for no creation. ?ENT-41 Undefined Network Node. ENTER UUO failure 41. The device "dev:" cannot be opened because the node on which it resides is not on line. Try again later. ENTER FAILURE "nn" on Output File "filespec" The attempted ENTER of the output file "filespec" has failed and the monitor has returned an error code of "nn". This error is not expected to occur on an ENTER. Please report it to your systems manager with the tty printout showing what you were doing. Standard TECO PAGE 7-8 Error Messages ?EOA nEO Argument Too Large The argument "n" given with an EO command is larger than the standard (maximum) setting of eo="2" for this version of TECO-10. This must be an older version of TECO-10 than the user thinks he is using; the features corresponding to EO="n" do not exist. ?FNF-00 Input File "filespec" not Found LOOKUP UUO failure 0. The file "filespec" specified for input by an ER, EB, EI, EP, OR TECO command was not found on the input device "dev:". ?FNF-01 Input UFD - not Found LOOKUP UUO failure 1. The file "filespec" specified for input by an ER, EB, EI, EP, OR TECO command cannot be found because there is no User File Directory with project-programmer number "[p,pn]" on device "dev:". ?FNF-02 Input Protection Failure LOOKUP UUO failure 2. The file "filespec" specified for input by an ER, EB, EI, EP OR TECO command cannot be read because it is read-protected "" against the user. ?FNF-06 Input UFD or RIB Error LOOKUP UUO failure 6. The input file "filespec" cannot be read because a bad directory block was encountered by the monitor while the LOOKUP was in progress. The user may try repeating the ER, EB, EI, EP OR TECO command, but if the error persists all is lost. Notify your system manager. ?FNF-16 Monitor Table Space Exhausted LOOKUP UUO failure 16. The input file "filespec" cannot be read because there is not enough table space left in the monitor to allow the LOOKUP. The user may try repeating the ER, EB, EI, EP, OR TECO command, but if the error persists he or she will have to wait until conditions improve. ?FNF-23 Input SFD not Found LOOKUP UUO failure 23. The input file "filespec" cannot be found because the sub-file-directory on which it should be looked up cannot be found. ?FNF-24 Search List Empty LOOKUP UUO failure 24. The input file "filespec" cannot be found because the user's file structure search list is empty. Standard TECO PAGE 7-9 Error Messages ?FNF-25 Input SFD Nested Too Deeply LOOKUP UUO failure 25. The input file "filespec" cannot be found because the specified SFD path for the LOOKUP is nested too deeply. ?FNF-41 Undefined Network Node. LOOKUP UUO failure 41. The device "dev:" cannot be opened because the node on which it resides is not on line. Try again later. Lookup Failure ("nn") on Input File "filespec" The attempted LOOKUP on the input file "filespec" has failed and the monitor has returned an error code of "nn". This error is not expected to occur on a LOOKUP. Please give the terminal prinout showing what you were doing to your system manager. ?ICE Illegal ^E Command in Search Argument A search argument contains a ^E command that is either not defined or incomplete. The only valid ^E commands in search arguments are: ^EA, ^ED, ^EV, ^EW, ^EL, ^ES, ^E, and ^E[A,B,C,...]. ?ICN Illegal ^N Command in Search Argument When used in a search argument, the ^N command must be followed by a character. ?ICT Illegal Control Command "^x" in Text Argument The character "^x" is neither a printing control character nor a valid control command in a text string. TO RECOVER: immediately type "*81EOM8". The character "x" is legal text if EO=1. Alternatively, retype the string with the control characters preceded by ^Q, ^R, or ^T. ?IDV Input Device "dev:" not Available INITIALIZATION FAILURE. Unable to initialize the device "dev:" for input. Either the device is being used by someone else right now, or else it does not exist in the system. ?IEM Re-Init Failure on Device "dev:" After EM Unable to re-initialize the device "dev:" after executing an EM command on it. If this error persists after retrying to initialize the device with an ER command(or EW command if output to the device is desired), consult your system manager. ?IER Input Error While Reading a File While reading an initialization, EI, EP, etc. an i/o error occurred. Standard TECO PAGE 7-10 Error Messages ?IES Input Error While Reading SWITCH.INI An I/O error occurred whilst reading SWITCH.INI. ?IFC Illegal Character "^x" After F "F" was interpreted as part of a 2-letter command. "F"^x" is not recognized as a command. ?IFS Illegal Character "^x" in File Specification File specifications must be of the form: DEV:FILE.TXT[PATH] where DEV, FILE, and EXT are alphanumeric strings. No characters other than these may appear between the EB, ED, EE, EI, EN, EP, EW, or EZ command and the altmode terminator ($). ?ILL Illegal Command: "^x" The character "^x" is not defined as a valid TECO-10 command. ?ILM Illegal Memory Reference TECO-10 made an illegal memory reference. This is an internal error and should be reported, along with a teletype printout showing what the user was doing. The value of the buffer pointer is set to the beginning of the buffer; the buffer and file should (hopefully) remain intact. ?ILR Cannot LOOKUP Input File "filespec" to RENAME it Failure in rename process at close of editing job initiated by an EB command or a TECO command. Unable to do a LOOKUP on the original input file "filespec" in order to RENAME it to "filnam.BAK". The output file is closed with the name "Filespec". The LOOKUP UUO error code is "nn". ?ILS Illegal EL Specification A numeric specification for the EL command must be greater than or equal to 0, and less than or equal to 3. ?INP Input Error "nn0000" on File "filespec" A read error has occurred during input. The input file "filespec" has been released. The user may try again to read the file, but if the error persists, the user will have to return to his or her backup file. The input device error flags (status word right half with bits 22-35 masked out) are "nn0000" ("nn0000") ?INP-01 BLOCK TOO LARGE. ?INP-02 PARITY OR CHECKSUM ERROR. ?INP-03 BLOCK TOO LARGE AND PARITY ERROR. Standard TECO PAGE 7-11 Error Messages ?INP-04 DEVICE ERROR, DATA MISSED. ?INP-05 BLOCK TOO LARGE AND DEVICE ERROR. ?INP-06 PARITY ERROR AND DEVICE ERROR. ?INP-07 BLOCK TOO LARGE, PARITY ERROR, AND DEVICE ERROR. ?INP-10 IMPROPER MODE. ?INP-11 BLOCK TOO LARGE AND IMPROPER MODE. ?INP-12 PARITY ERROR AND IMPROPER MODE. ?INP-13 BLOCK TOO LARGE, PARITY ERROR, AND IMPROPER MODE. ?INP-14 DEVICE ERROR AND IMPROPER MODE. ?INP-15 BLOCK TOO LARGE, DEVICE ERROR, AND IMPROPER MODE. ?INP-16 PARITY ERROR, DEVICE ERROR, AND IMPROPER MODE. ?INP-17 BLOCK TOO LARGE, PARITY ERROR, DEVICE ERROR, AND IMPROPER MODE. ?IPA Illegal argument to "P" command The "P" command can take a numeric argument, which is the number of pages to move. A negative argument is illegal. ?IPP Illegal Character "^x" in PPN A PPN is of the form [PJ,PG,SFD1,...,SFDN] where "PJ", "PG", and ",SFD1,...,SFDN" are optional. "PJ" and "PG" must be octal numbers. An SFD is an alphanumeric or quoted string. ?IPR Illegal Character "^x" in /PROTECT Switch The format of the /PROTECT switch is: /PROTECT:NNN Where NNN is an octal number and may optionally be enclosed in angle brackets (ie: /protect:) ?IQC Illegal Character "^x" after " Command The ONLY VALID " COMMANDS ARE "G, "L, "N, "E, "C, "R, "A, "D, "V, "W, "T, "F, "S, and "U. ?IQN Illegal Character "^x" in Q-Register Name A Q-register name must be in one 2 formats: (1) X , where "X" is a printing character (except `,{,|,},~) (2) (FOO) where "FOO" is up to 6 alphanumerics, or is in quotes. Standard TECO PAGE 7-12 Error Messages ?IQR Illegal Character "^x" in Q-Register Name, please retype The Q-register name given in the "*" command contains an illegal character. Re-type the "*" and a legal q-register name. A Q-register name must be in one 2 formats: (1) X , where "X" is a printing character (except `,{,|,},~) (2) (FOO) where "FOO" is up to 6 alphanumerics, or is in quotes. ?IRB Cannot Rename Input File "filespec" to "filnam.BAK" Failure in rename process at close of editing job initiated by an EB command or a TECO command. The attempt to rename the original input file "filespec" to the backup filename "filnam.BAK" has failed. The output file is closed with the name "Filespec". The RENAME UUO error code is "nn". ?IRN Cannot Re-Init Device "dev:" for Rename Process Failure in rename process at close of editing job initiated by an EB command or a TECO command. Cannot reinitialize the original input device "dev:" in order to rename the input file "Filespec" to "filnam.BAK". The output file is closed with the name "filespec". ?ISW Illegal Character "^x" in a Switch AN ARGUMENT WAS EXPECTED AFTER The SWITCH "/SWITCH". A COLON (:) WAS EXPECTED. ?ITT Illegal TTCALL Type Value "nn" The EXTENDED TTCALL command must take the form "arg1,arg2:^T" where arg1 is the (optional) TTCALL argument and arg2 is the TTCALL type in decimal. The second argument must be a legitimate TTCALL type, With 0-13 legal except for 3(OUTSTR). :8^T will do a RESCAN, :1,8^T tests for CCL entry point. ?IUU Illegal LUUO A local uuo was encountered which is not legal. This error should not occur. close your files and report this problem to your system manager. ?LDV Cannot Access Log Device I can't get that device for a log file, dummy! ?LFE Cannot ENTER Log File I can't make the file, dummy! Standard TECO PAGE 7-13 Error Messages ?LLB Linked-list broken This is an internal error. The linked list of q-register values, etc. is broken. Try to save your edits and exit. This is an internal error which should be reported. Save your output. ?MAP Missing ' Every conditional (opened with the " command) must be closed with the ' command. ?MCP Missing Control PDL A pdl overflow was trapped and the control pdl was found to be missing. This error should not occur. Close your files and report the problem to your system manager. ?MEF Macro Ending with F A command macro being executed from a Q-register ends with the character "F". This is an incomplete command. F is the initial character of an entire set of commands. The other character of the command begun by F must be in the same macro with the F. ?MEO Macro Ending with Unterminated O Command The last command in macro "q" is an "O" command with no delimiter to mark the end of the tag-name. ?MEQ Macro Ending with " The macro "q" ends with a " character. This is an incomplete command. " must be followed by G, L, N, E, C, A, D, V, W, T, F, S, or U to indicate the condition under which the following commands are to be executed. This character must be in the Q-register with the ". ?MEU Macro Ending with ^ The macro "q" ends with a ^ character. This is an incomplete command. ^ followed by a character converts the character into a control character for command parsing. The character was not there. ?MIQ Macro Ending with "^x" The macro "q" ends with the "^x" command. This command requires a Q-register name of 1 character or up to 6 characters in parentheses. ?MLA Missing Left Angle Bracket There is a right angle bracket that has no matching left angle bracket. An iteration must be complete within the macro or command. Standard TECO PAGE 7-14 Error Messages ?MLP Missing ( There is a right parenthesis that is not matched by a corresponding left parenthesis. ?MRA Missing Right Angle Bracket There is a left angle bracket that has no matching right angle bracket. An iteration must be complete within the macro or command. ?MRP Missing ) There is a right parenthesis that is not matched by a corresponding left parenthesis. ?MSC Missing Start of Conditional A ' command (end of conditional) was encountered. Every ' command must be matched by a preceding " (start of conditional) command. ?MUU Macro Ending with ^^ The macro "q" ends with either a control-^ or ^^. This is an incomplete command. The ^^command takes a single character text argument that must be in the Q-register with the ^^. ?NAE No Argument Before = The command N= or N== causes that value N to be typed. The = command must be preceded by either a specific numeric argument or a command that returns a numeric value. ?NDI No Delimiter After I If the I command has a numeric argument it must be followed by a null text string i.e.: 33I$ or 33@i// ?NAQ No Argument Before " The " command must be preceded by a single numeric argument on which the decision to execute the following commands or skip to the matching ' is based. ?NAU No Argument Before U The command NUI stores the value N in Q-register I. The U command must be preceded by either a specific numeric argument or a command that returns a numeric value. Standard TECO PAGE 7-15 Error Messages ?NFI No File for Input Before issuing an input command (Y, ^Y, or A) it is necessary to open an input file by use of an ER, EB, or TECO command. ?NFO No File for Output Before giving an output command (PW, P, ^P, N, EX, or EG) it is necessary to open an output file by use of an EA, EB, EW, EZ, MAKE, or TECO command. ?NLF No Log File Open A command of the form nEL was given, but there is no log file open to have parameters modified. ?NSI Null Switch Name is Illegal A switch name must consist of one or more alphanumeric characters. ?NTQ No text in Q-register The Q-register "q" does not contain text. ?NYA Numeric argument to "Y" or "EY" command The "Y" command does not take numeric arguments. Did you type "0YY" instead of "0TT"? ?ODV Output Device "dev:" Not Available Initialization failure. Unable to initialize the device "dev:" for output. Either the device is being used by someone else right now, or it is write locked, or else it does not exist in the system. ?OFO EW Before Current Output file Closed An EB,EW,EA, or EZ command may not be given while an output file is open. Give an EF to close the file if you wish to save the output file as it is, or an EK to throw away the current output file. ?OUT Output Error "nn0000". Output File "filespec" Closed An error on the output device is fatal. The output file is closed at the end of the last data that was successfully output. It has the filename "Filespec". See the TECO Reference Manual section 4.4 for a recovery technique. The output device flags (status word right half with bits 22-35 masked out) are "nn0000" ("nn0000") ?OUT-00 End of Tape. Standard TECO PAGE 7-16 Error Messages ?OUT-01 Block Number Too Large, Device Full or Quota Exceeded. ?OUT-02 Parity or Checksum Error. ?OUT-03 Block Number Too Large and Parity Error. ?OUT-04 Device Error, Data Missed. ?OUT-05 Block Number Too Large and Device Error. ?OUT-06 Oarity Error and Device Error. ?OUT-07 Block Number Too Large, Parity Error, & Device Error. ?OUT-10 Improper Mode or Device Write Locked. ?OUT-11 Block Number Too Large and Improper Mode. ?OUT-12 Parity Error and Improper mode. ?OUT-13 Block Number Too Large, Parity Error, & Improper Mode. ?OUT-14 Device Error & Improper Mode. ?OUT-15 Block Number Too Large, Device Error, & Improper Mode. ?OUT-16 Parity Error, Device Error, and Improper Mode. ?OUT-17 Block Number Too Large, Parity Error, Device Error, and Improper Mode. ?OWL OUTPUT ERROR writing LOG FILE AN OUTPUT ERROR OCCURED, DUMMY! ?PAR Confused Use of Parentheses An iteration may not be contained within a parenthesized expression. ?PES Attempt to Pop Empty Stack A ] command (pop off q-register stack into a q-register) was encountered when there was nothing on the q-register stack. ?PNF Page Number "nn" Not Found An attempt to move to page "nn" of the input file "filespec" was made with the ^P or ^Y command. that page does not exist in the input file. Standard TECO PAGE 7-17 Error Messages ?POP Attempt to move Pointer Off Page. The argument specified with a J, C, R, or D command must point to a position within the current size of the buffer. (ie: between B and Z inclusive.) This can also occur on a "]()" command since the numeric value will be used for ".". This can also occur with the nA command (A with numeric argument) if (.+n) attempts to access a character off either end of the buffer. ?PPC Attempt to Move Previous to Current page with ^P or ^Y The argument to a ^P or ^Y command is an absolute page number in the file. it must be greater than or equal to the current page number. ?PTS PDL Table Too Small There are not enough ENTRIES in the pdl table. This error is not expected to occur. Close your files and report the problem to your system manager. ?RNF-01 UFD for "filespec" Not Found RENAME UUO failure 1. The new filespec "Filespec" specified by an EN command cannot be used because there is no directory "[p,pn]" on device "dev:". ?RNF-02 Protection Failure for "Filespec" RENAME UUO faulure 2. the filespec "Filespec" specified by an EN command cannot be used because you are not privileged to RENAME the input file. ?RNF-03 File Being Modified RENAME UUO failure 3. The filespec "filespec" specified by an EN command cannot be used because the input file is being modified by someone. ?RNF-04 Rename Filename "filespec" already exists RENAME UUO failure 4. The filespec "filespec" specified by an EN command could not be used because there is already a file by that name. ?RNF-06 UFD or RIB Error RENAME UUO failure 6. The filespec "filespec" specified by an EN command could not be used because a bad directory block was encountered by the monitor. Notify your system manager. Standard TECO PAGE 7-18 Error Messages ?RNF-22 Cannot Delete a Non-Empty Directory RENAME UUO failure 22. The filespec "filespec" specified by an EN command could not be used because the input file was a directory which was not empty, and therefore cannot be deleted. ?RNF-23 Output SFD Not Found RENAME UUO failure 23. The output file "filespec" specified by an EN command could not be used because the Sub-File-Directory on which the file should be placed does not exist. RENAME failure "nn" for "filespec" The attempted Rename of the Input file has failed and the monitor has returned an error code of "nn". This error should probably not happen on a RENAME. Please report the problem to your systems manager. ?RNO Cannot Rename Output File "Filespec" Failure in rename process at close of EDITING job initiated by an EB command or a TECO command. The attempt to rename the output file "Filespec" to the name "filespec" originally specified in the EB or TECO command has failed. The original input file "filespec" as been renamed "filnam.BAK", BUT The OUTPUT FILE IS CLOSED WITH The NAME "Filespec". The RENAME UUO error code is "nn". ?SAL Second Argument Less Than First In a two argument command, the first argument must be less than or equal to the second. ?SEF Superceding Existing File: "filespec" The output file "filespec" already exists on "dev:". This message is warning the user that his or her existing file is being overwritten. ?SNA Initial Search With No Argument A search command with null argument has been given, but there was no preceding search command from which the argument could be taken. ?SNI ; Not in Iteration The semicolon command may be used only in an iteration. ?SRH Cannot Find "string" A search command not preceded by a colon modifier and not within an iteration has failed to find the specified character string "string". If an S, FS, FD, or any negative or bounded search fails, the pointer is unchanged. After an n or _ search fails, the last page of the input file has been read and, in the case of N, output, and the buffer cleared. Standard TECO PAGE 7-19 Error Messages ?STC Search String Too Long The maximum length of a search string is 80 characters, including all string control commands and their arguments. ?STL Search String Too Long The maximum length of a search string is 36 character positions, not counting extra characters required to specify a single position. ?TAG Missing Tag !tag! The tag !tag! specified by an O command cannot be found. This tag must be in the same macro level as the O command referencing it. ?TAL Two Arguments With L The L command takes at most one numeric argument, namely, the number of lines over which the buffer pointer is to be moved. ?TSD Too Many Nested SFD'S The number of Sub-File-Directories specified in a path exceeds the number allowed by TECO-10. IF DESIRED, The USER MAY RE-ASSEMBLE TECO-10 WITH 'C$SFDL' EQUAL TO The DESIRED NESTING LEVEL OF SFD'S. ?TTY Illegal TTY I/O Device A teletype may be specified as an input/output device in an ER, EW, EZ, or MAKE command only if it is not being used to control an attached job, the user's own terminal. ?UAT Unenabled APR Trap An APR trap occurred which was not enabled. This error should not occur. Please report it to your systems manager. ?UCA Unterminated ^A Command A ^A message type-out command has been given, but there is no corresponding ^A to mark the end of the message. ^A commands must be complete within a single macro level. ?UEN Unimplemented "EN" command The EN command is not implemented, sorry. ?UFS Macro Ending with Unterminated File Selection Command The last command in the macro "q" is a file selection command (ER, EW, EB, ED, EL, EI, EN, or EZ) with no delimiter to mark the end of the file specification. The file selection command must be complete within the Q-register. ?UIN Unterminated Insert Command Standard TECO PAGE 7-20 Error Messages ?UIN Unterminated Insert Command An insert command (possibly an @ insert command) has been given without terminating the text argument at the same macro level. ?UQN Unterminated Q-Register Name (missing ) ) If a multi-character q-register name is specified, it must be terminated by a right parenthesis. the format is: ) > ?USN Unknown Switch Name: "SWITCH" The switch "/SWITCH" is not defined with either input or output file selection commands. The currently implemented switches are: /PROTECT, /ASCII, /LSN, /NOIN, /NOOUT, /APPEND, /SIXBIT, /OCTAL, /NONSTD, /GENLSN, and /SUPLSN. ?USR Unterminated Search Command A search command (possibly an @ search command) has been given without terminating the text argument at the same macro level. ?UTG Unterminated Tag A command string tag has been indicated by a ! command, but there is no corresponding ! to mark the end of the tag. Tags must be complete within a single command level. ?VAI Version incompatability The current version of TECO-10 may be incompatable with save files written with the EE command with an old version of TECO-10. Re-compile all your macros and re-issue the EE command if possible. If this is not possible, it may be possible to continue, but random errors may occur. ?XTB Attempt to execute the Text editing Buffer. The Q-register "q" is currently sharing with the blank Q-register, which is the Text-editing buffer. Do "HXqMq". ?XXX Should Not Occur. Please report this problem to your systems manager as soon as possible. sorry for the inconvenience. try to close your files if possible. ?YCA "Y" or "_" command aborted due to non-empty buffer The "Y" and "_" commands are only legal if the editing buffer is empty, or if 2ED is set, or in a macro. "EY" is the same command as "Y" but without this restriction. "E_" is the same command as "_" but without this restriction. Standard TECO PAGE 7-21 Error Messages 7.2.3 TECO-8 ERROR MESSAGES ?ARG Improper Arguments The following argument combinations are illegal: 1) , (no argument before comma) 2) m,n, (more than two arguments) 3) H, (because H=B,Z is already two arguments) ?MEM Storage Capacity Exceeded The current operation requires more memory storage for text (in the text buffer) than TECO has available. In 8K machines, there is room for at most xxxx characters of text. On larger machines, there is room for 4000 (decimal) characters. ?FER File Error File error can mean one of five things: 1) Input file not found on an ER command 2) Error while trying to enter the output file on an EW or EB command 3) The device specified in a file specification does not exist 4) EB command given on a non-file-structured device 5) Attempt to perform an EB on a file with a .BK extension ?FUL Output Command would have Overflowed An output command such as P, EX, EC, EG, PW, N, or FN would have written more data to the output file than there was room allocated on the output device. The data that would have overflowed the output device is still in the text buffer and has not been written out. You can close the output file with an EF command and then open a new output file and continue editing. When you are all done, PIP can be used to merge the two output files back into one. ?IEC Illegal Character "x" after E The only commands starting with the letter E are EB, EC, ED, EF, EG, EH, EK, EO, ER, ES, ET, EU, EW, EX and EY. When used as a command (i.e. not in a text argument), E may not be followed by any character except one of these. Secondary I/O streams (EA, EP, EI), magtape commands (EM), wildcard lookups (EN), and device initialization (EZ) are not available in TECO-8. The ES flag does not currently do anything. Standard TECO PAGE 7-22 Error Messages ?IFC Illegal Character "x" after F The only commands starting with the letter F are FS, F, and FN. When used as a command (other than EF or in a text argument), F may not be followed by any character other than one of these. The S, , or N must immediately follow the F with no intervening spaces or commands. The two characters in an F command may not be split across macros. The FR command is not implemented in TECO-8. ?IFN Illegal Character "x" in Filename File specifications must be in the form dev:filnam.ext where dev, filname, and ext are alphanumeric. The file specification may optionally end with a /S which means ignore end-of-file on any subsequent input. No characters other than the ones specified may appear in a text argument to an ER, EW, or EB command. ?ILL Illegal Command "x" The specified character is not defined as a valid TECO command. (The W command is only available with VT support.) ?INP Input Error An I/O error occurred while trying to read from the input file. ?IQC Illegal Character "x" after " The only valid " commands are "C, "R execute if alphanumeric "E, "= execute if = 0 "F, "U execute if unsuccessful "L, "< execute if less than 0 "G, "> execute if greater than 0 "N execute if not equal to 0 "S, "T execute if successful "D execute if digit "A execute if alphabetic The commands "V, and "W are not available in TECO-8. ?IQN Illegal Q-register Name "q" The Q register name specified by a command such as Q, U, X, G, %, or M must be a letter (A-Z) or a digit (0-9). Pseudo-Q-registers and * are not available in TECO-8. ?ISA Negative or Zero Argument to S The argument preceding a search command indicates the number of times a match must be found before the search is considered successful. This argument must be greater than 0. Backward searches and bounded searches are not permitted in TECO-8. Standard TECO PAGE 7-23 Error Messages ?UTM Unterminated Macro A command macro being executed from a Q-register terminated with an incomplete command, such as 1) macro ended with with only one character of a two character command (such as F, E, or ^) 2) macro ended with a command that requires a Q-register name (such as X, G, M, %, Q, U, or ^U) but no Q-register name was specified 3) macro ended with a command that takes a string argument (such as ERfile$, Itext$, Stext$, Otag$, etc.) and the text argument was not properly terminated by an ALTMODE (or the specified delimiter if the at-sign form was used) 4) An O command was issued and the specified tag was not found in that macro (subsequent to the start of the current iteration) ?BNI > not in an Iteration There is a right angle bracket not matched by a left angle bracket somewhere to its left. (Note: an iteration in a macro stored in a Q-register must be complete within the Q-register.) ?NAE No Argument before = The command n= or n== causes the value of n to be typed. The = command must be preceded by either a specific numeric argument or a command that returns a numeric value. ?NAQ No Argument before quote The " command must be preceded by a single numeric argument on which the decision to execute the following commands or skip to the matching ' is based. ?NAU No Argument before U The command nUq stores the value n in Q-register q. The U command must be preceded by either a specific numeric argument or a command that returns a numeric value. ?NFO No File for Output Before giving an output command (P, PW, N, EC, or EG) it is necessary to open an output file by use of an EB, EW, MAKE or TECO command. To prevent possible loss of data, the EX, EC, and EG commands will be aborted if there is no output file open and there is text in the text buffer. The HKEX command will always work. To abort TECO immediately, use the ^C command. Standard TECO PAGE 7-24 Error Messages ?POP Attempt to Move Pointer Off Page with "x" The argument specified with a J, C, or R command must point to a position within the current size of the text buffer, i.e. between 0 and Z inclusive. The argument to commands that reference pointer positions, such as nA or m,nP or m,nK must reference buffer pointer positions bewteen 0 and Z inclusive. ?POP Reference to Pointer Position Off Page with "x" Command The argument specified with a J, C, or R command must point to a position within the current size of the text buffer, i.e. between 0 and Z inclusive. The argument to commands that reference pointer positions, such as nA or m,nP or m,nK must reference buffer pointer positions bewteen 0 and Z inclusive. ?DTB Delete too big A D command was issued with an argument that was so large that the command would delete character positions outside the current buffer. The D commmand may only delete existing characters. No characters were deleted. ?OUT Output Error An error occurred while trying to write to the output file, or there was not enough room to enter the file on an EW or EB command. ?SNI ; not in an Iteration The semicolon command was used at command level. The ; command may only be used within a string of commands enclosed by angle brackets, i.e. an iteration field. ?SRH Search failed "string" A search command not preceded by a colon modifier and not within an iteration has failed to find the specified character string. After an S (or FS) search fails, the buffer pointer is left positioned at the beginning of the buffer. After an N or search fails, the last page of the input file has been input and, in the case of N, output, and the buffer cleared. The string that you were searching for is shown in the one-line error message. Note that the special search characters CTRL/N, CTRL/S, and CTRL/X are indicated in this string as "^E". Backward searches and bounded searches are not permitted in TECO-8. Anchored searches are also not permitted. Note that the action of "^" in search strings depends on the setting of the ED&1 bit. If 0, then ^ means convert next character to its control character. Standard TECO PAGE 7-25 Error Messages ?STL Search String too Long The maximum length of a search string is 31 characters (38 characters if you have no VR12 or VT scope support). ?UTC Unterminated Command An incomplete command has been given. This could be caused by any of the following: 1) A command that requires a text string (such as @ER/file/, @S/text/, ^Atext^A, etc.) ended the command string, but the text argument was not properly terminated. 2) An O command was issued and the specified tag was not found in the command string subsequent to the start of the current iteration. ?PDO Internal Push Down Overflow Your macros and iterations have been nested too deeply. ?QMO Q-register Memory overflow There is not enough room allocated to Q-register storage and command string storage to satisfy the current command. If you were typing a command string when you got this error message, you might be able to recover most of the command string by immediately typing CTRL/S as the very next command, thus putting the previous command string into Q-register Z. ?NYA Numeric Argument to Y The Y command may not be preceded by a numeric argument. To yank multiple pages, use the n command. ?NPA Negative or Zero Argument to P The argument to a P command specifies the number of times the P command is to be executed. This argument must be positive. ?NCA Negative or Zero Argument to , The number before a comma refers to a position within the text buffer. This value must be between 0 and Z inclusive and may not be negative. ?NYI Case Support not Implemented [use W for Watch Command] The case control commands ^V and ^W are not available in TECO-8. To get TECOs version number, issue the EO command. To use the watch command (with VR12 or VT support) use the W command. Also, the push [ and pop ] commands are not implemented in TECO-8. Standard TECO PAGE 7-26 Error Messages ?NYI Case Support not Implemented [Use EO for Version number] The case control commands ^V and ^W are not available in TECO-8. To get TECOs version number, issue the EO command. To use the watch command (with VR12 or VT support) use the W command. Also, the push [ and pop ] commands are not implemented in TECO-8. ?UIS Undefined I/O Switch The only I/O switch that is defined in TECO-8 is the /S switch. ?WLO Cannot Write Out Error Message Overlay The system device is write-locked. ?YCA Y or _ Command Aborted To prevent accidental loss of data, the commands Y, and F will abort if there is text in the text buffer and there is an output file open. If you don't care about the output file, you can kill it with the EK command. The HKY command is always permitted. Yank protection can be disabled by clearing bit 10 of the ED flag, i.e. by issuing the TECO command: ED&1ED This command may be put into your TECO.INI if you dislike yank protection. ?CCL CCL.SV not found or EG argument too big You issued a command of the form EGcommand$ and the specified command was too large (more than 43 characters) or CCL.SV was not found on the system device. ?XAB Execution aborted Execution of your TECO command or command input was aborted because you typed a CTRL/C. To get out of TECO, type a CTRL/C immediately after TECO's prompt. If you accidentally got back to monitor level there is a slight chance that you can get back to TECO by using ODT to restart your core image at location 203. ?ICE Extended CTRL/E match control not implemented The character CTRL/E is not permitted within a search string. This character is reserved for special use in future versions of TECO-8. Note that the presence of a "^E" in the string printout within the ?SRH error message denotes the presence of one of the special match control constructs, CTRL/N, CTRL/X, or CTRL/S. Standard TECO Page 7-27 Error Messages ?NAB No Argument Before ^_ The one's complement command ^_ was used without a numeric argument. The form of the command is n^_ and the command returns the one's complement of the argument n. ^_ is not a unary operator and must be used after a numeric argument (not before it). ?UEx Unimplemented character "x" after E The commands EA, EI, EL, EM, EN, EP, EV, and EZ are not implemented in TECO-8. The only legal E commands are EBfilespec$ Edit Backup EC closes output file after moving across input EF closes output file EG$ performs EX then re-executes last compile class EGcommand$ performs EX then executes command specified EK kills output file ERfilespec$ Opens file for input EWfilespec$ Opens file for output EX moves across input to output file, then closes it and exits TECO EY unprotected Y command The following commands are valid flags: ED, EH, EJ, EO, ES, ET and EU. Standard TECO PAGE 7-28 Error Messages Standard TECO Page A-1 Appendix A APPENDIX A OCTAL & DECIMAL ASCII CHARACTER SET CHAR OCT DEC CHAR OCT DEC CHAR OCT DEC CHAR OCT DEC NUL 000 000 SP 040 032 @ 100 064 ` 140 096 ^A 001 001 ! 041 033 A 101 065 a 141 097 ^B 002 002 " 042 034 B 102 066 b 142 098 ^C 003 003 # 043 035 C 103 067 c 144 099 ^D 004 004 $ 044 036 D 104 068 d 144 100 ^E 005 005 % 045 037 E 105 069 e 145 101 ^F 006 006 & 046 038 F 106 070 f 146 102 ^G 007 007 ' 047 039 G 107 071 g 147 103 ^H 010 008 ( 050 040 H 110 072 h 150 104 TAB 011 009 ) 051 041 I 111 073 i 151 105 LF 012 010 * 052 042 J 112 074 j 152 106 VT 013 011 + 053 043 K 113 075 k 153 107 FF 014 012 , 054 044 L 114 076 l 154 108 CR 015 013 - 055 045 M 115 077 m 155 109 ^N 016 014 . 056 046 N 116 078 n 156 110 ^O 017 015 / 057 047 O 117 079 o 157 111 ^P 020 016 0 060 048 P 120 080 p 160 112 ^Q 021 017 1 061 049 Q 121 081 q 161 113 ^R 022 018 2 062 050 R 122 082 r 162 114 ^S 023 019 3 063 051 S 123 083 s 163 115 ^T 024 020 4 064 052 T 124 084 t 164 116 ^U 025 021 5 065 053 U 125 085 u 165 117 ^V 026 022 6 066 054 V 126 086 v 166 118 ^W 027 023 7 067 055 W 127 087 w 167 119 ^X 030 024 8 070 056 X 130 088 x 170 120 ^Y 031 025 9 071 057 Y 131 089 y 171 121 ^Z 032 026 : 072 058 Z 132 090 z 172 122 ALT 033 027 ; 073 059 [ 133 091 { 173 123 FS 034 028 < 074 060 \ 134 092 | 174 124 GS 035 029 = 075 061 ] 135 093 } 175 125 RS 036 030 > 076 062 ^ 136 094 ~ 176 126 US 037 031 ? 077 063 _ 137 095 DEL 177 127 Standard TECO Page A-2 Appendix A Standard TECO Page B-1 Appendix B APPENDIX B ERROR MESSAGES TECO error messages consist of a three letter message preceded by a question mark (?) or proceeded by ?TEC. A short description of the error optionally follows (dependent on the current value of the EH flag). Typing ? (question mark) immediately after an error message printout causes the command string to be printed up to and including the character which causes the error message. Typing *q (asterisk, Q-register name) immediately after an error message printout saves the entire command string in the specified Q-register. This is especially useful for recovering mistyped insert commands. Both the ? and *q facilities may be used when an error occurs. TECO-11 also produces two warning messages. These messages do not abort the command and execution continues. %Superseding existing file Indicates that the file to be created as the result of an EW command already exists. If the output file is closed the old copy of the file will be deleted. The EK command may be used to "take back" the EW command. %Search fail in iter Indicates that a search command has failed inside iteration brackets. A ; (semi-colon) command immediately following the search command can typically be used to suppress this message. These error messages are listed alphabetically by their three-letter code. In general, these three-letter codes have the same meaning on all implementations, although not all error messages are produced by each implementation. The one-line error message given here is a paraphrasing of the message given, which may differ slightly from system to system. Standard TECO Page B-2 Appendix B ?ARG Improper Arguments Three arguments are given (a,b,c or H,c). ?BNI > not in iteration There is a close angle bracket not matched by an open angle bracket somewhere to its left. (Note: an iteration in a macro stored in a Q-register must be complete within the Q-register.) ?CCL CCL.SV not found or EG argument too long The EGcommand$ command on OS/8 was unable to locate SYS:CCL.SV or the specified command has more than 46 characters. ?CPQ Can't pop into Q-register A ] command has been executed and there is nothing saved on the Q-register push down list. ?DEV Invalid device A file specification string in an E command contains an unknown device name. ?DTB Delete too big An nD command has been attempted which is not contained within the current page. ?ERR RSTS/E error message (RSTS/E only) Some RSTS/E monitor call failed. The error message text explains the error. ?FER File Error The file specified in an ER, EW or EB command was not found. ?FNF File not found "filespec" The requested input file could not be located. If this occurred within a macro the colon modified ER or EB command may be necessary. ?FUL Output Command would have overflowed output device The page of text currently in the text buffer will not fit in the open output file. Until enough free space can be obtained on the output device the file may have to be split. An EF command to close the current output file, followed by a new EW command to a temporary file may be used. The files should be concatenated when the space problem is alleviated. Standard TECO Page B-3 Appendix B ?IEC Illegal character "x" after E An invalid E command has been executed. The E character must be followed by an alphabetic to form a legal E command (i.e., ER or EX). ?IFC Illegal character "x" after F An invalid F command has been executed. The only valid F commands are FB, FC, FD, FK, FN, FR, FS, and F_. ?IFN Illegal character "x" in filename The filespec as an argument to one of the E commands is unacceptable to the system. The file specification must be appropriate to the system in use. ?IIA Illegal insert arg A command of the form "nItext$" was attempted. This combination of character and text insertion is illegal. ?ILL Illegal command "x" An attempt has been made to execute an invalid TECO command. ?ILN Illegal number An 8 or 9 has been entered when the radix of TECO is set to octal. ?INP Input error The system has reported an error attempting to read the current input file. The text buffer may be corrupt. This operation may be retried, but if the error persists, you may have to return to a backup file. ?IPA Negative or 0 argument to P The argument preceding a P or PW command is negative or 0. ?IQC Illegal " character One of the valid " commands did not follow the ". Refer to Section 5.14 (conditional exectution commands) for the legal set of commands. ?IQN Illegal Q-reg name "x" An illegal Q-register name was specified in one of the Q-register commands. ?IRA Illegal radix argument to ^R The argument to a ^R radix command must be 8, 10, or 16. ?ISA Illegal search arg Standard TECO Page B-4 Appendix B The argument preceding a search command is 0. This argument must not be 0. ?ISS Illegal search string One of the search string special characters (^Q, ^V, ^W, etc.) would have modified the search string delimiter (usually ESCAPE). ?IUC Illegal character "x" following ^ The character following an ^ must have ASCII value between 100 and 137 inclusive or between 141 and 172 inclusive. ?MEM Memory overflow Insufficient memory available to complete the current command. Make sure the Q-register area does not contain much unnecessary text. Breaking up the text area into multiple pages might be useful. (See section 5.19.) ?MFN Missing file name An ER or EW command has been executed in which the file name has been left out. ?MRP Missing ) A command string has been executed which contains a parenthetical expression that is not closed by a right parenthesis. ?NAB No arg before ^_ The ^_ command must be preceded by either a specific numeric argument or a command that returns a numeric value. ?NAC No arg before , A command has been executed in which a , is not preceded by a numeric argument. ?NAE No arg before = The = or == command must be preceded by either a specific numeric argument or a command that returns a numeric value. ?NAP No arg before ) A ) parenthesis has been encountered and is not properly preceded by a specific numeric argument or a command that returns a numeric value. Standard TECO Page B-5 Appendix B ?NAQ No arg before " The " commands must be preceded by a single numeric argument on which the decision to execute the following commands or skip to the matching ' is based. ?NAS No arg before ; The ; command must be preceded by a single numeric argument on which the decision to execute the following commands or skip to the matching > is based. ?NAU No arg before U The U command must be preceded by either a specific numeric argument or a command that returns a numeric value. ?NCA Negative argument to , A comma was preceded by a negative number. ?NYA Numeric argument with Y The Y command must not be preceded by either a numeric argument or a command that returns a numeric value. ?NFI No file for input Before issuing an input command, such as Y, it is necessary to open an input file by use of a command such as ER or EB. ?NFO No file for output Before issuing an output command such as N search or P it is necessary to open an output file by use of a command such as EW or EB. ?NPA Negative or 0 argument to P A P command was preceded by a negative or 0 argument. ?NRO No room for output The output device is too full to accept the requested output file. ?NYI Not Yet Implemented A command was issued that is not yet implemented in this version of TECO. ?OFO Output file already open A command has been executed which tried to create an output file, but an output file currently is open. It is typically appropriate to use the EC or EK command as the situation calls for to close the output file. Standard TECO Page B-6 Appendix B ?OUT Output error The system has reported an error attempting to do output to the output file. Make sure that output device did not become write locked. Use of the EF command (or EK if necessary) and another EW can be considered until the condition is fixed. ?PDO Push-down list overflow The command string has become too complex. Simplify it. ?POP Attempt to move Pointer Off Page with "x" A J, C or R command has been executed which attempted to move the pointer off the page. The result of executing one of these commands must leave the pointer between 0 and Z, inclusive. The characters referenced by a D or nA command must also be within the buffer boundary. ?SNI ; not in iteration A ; command has been executed outside of an open iteration bracket. This command may only be executed within iteration brackets. ?SRH Search failure "text" A search command not preceded by a colon modifier and not within an iteration has failed to find the specified "text". After an S search fails the pointer is left at the beginning of the buffer. After an N or _ search fails the last page of the input file has been input and, in the case of N, output, and the buffer is cleared. In the case of an N search it is usually necessary to close the output file and reopen it for continued editing. ?STL String too long A search or file name string is too long. This is most likely the result of a missing ESCAPE after the string. ?UEA EA not implemented The EA command has no meaning in this version of TECO. ?UEI Edit Indirect not implemented The EI command has no meaning in this version of TECO. ?UEN Edit Next not implemented The EN command has no meaning in this version of TECO. Standard TECO Page B-7 Appendix B ?UEP EP not implemented The EP command has no meaning in this version of TECO. ?UTC Unterminated command "x" This is a general error which is usually caused by an unterminated insert, search, or filespec argument, an unterminated ^A message, an unterminated tag or comment (i.e., unterminated ! construct), or a missing ' character which closes a conditional execution command. ?UTM Unterminated macro This error is the same as the ?UTC error except that the unterminated command was executing from a Q-register (i.e., it was a macro). (Note: An entire command sequence stored in a Q-register must be complete within the Q-register.) ?XAB Execution aborted Execution of TECO was aborted. This is usually due to the typing of . ?WLO System Device Write-Locked TECO-8 needs to write on the system device when it is running in less than 16K (less than 20K if VT52 is present) so that it can later swap in overlays. ?YCA Y command aborted An attempt has been made to execute an Y or _ search command with an output file open, that would cause text in the text buffer to be erased without outputting it to the output file. The ED command (section 5.16) controls this check. ?nnn I/O Error or Directive Error (RSX-11 only) All errors from the executive and file system are reported in this format, where nnn is the decimal I/O or directive error status. The accompanying message is the corresponding message from the QIOSYM message file. A complete list of I/O and directive errors appears in appendices to the various Executive reference manuals and in the IAS/RSX-11 I/O Operations Reference Manual. Standard TECO Page B-8 Appendix B Standard TECO Page C-1 Appendix C APPENDIX C Incompatible, Obsolete, and System-Specific Commands This appendix describes commands that are peculiar to specific operating systems. These commands fall into many categories. Some are obsolete, and are kept around only as a convenience to the user. Others are so system specific or so obscure that it was felt best not to include them in the main body of the manual. Some are incompatible across operating systems. Some are new commands that have not become firmly established and may change in the future. In general, use these commands at your own risk and with the understanding that in future releases of TECO, these commands may change or go away completely. Implementors of TECO on other operating systems should contact the TECO SIG before implementing any of these features. C.1 SPECIFIC FEATURES OF TECO-11 C.1.1 TECO COMMANDS Command Description m,nStext$ Performs the same function as the nS command, but m serves a bound limit for the search. If the search string can be found without moving the pointer more than ABS(m)-1 places, the search succeeds and the pointer is repositioned to immediately after the last character of the string. Otherwise, the pointer is left unchanged. The ^Q operator, described below, is useful in conjunction with this command. Note that m,Stext$ is identical to m,1Stext$ and m,-Stext$ is identical to m,-1Stext$. m,-nStext$ Performs the same function as the m,nS command, but searches is the reverse direction. 0,nStext$ Performs the same function as the nS command, except that the pointer position will remain unchanged on search string failure. (Essentially an unbounded search with no pointer movement on failure.) G* Get most recent filespec string. The asterisk represents TECO's filespec string area, which contains the fully expanded filespec of the last E command (see Standard TECO Page C-2 Appendix C appendices). Copy the contents of the filespec string area into the buffer at the current position of the buffer pointer, leaving the pointer positioned after the last character copied. :G* Print the contents of the filespec buffer on the terminal. G_ Get most recent search string. The underscore (backarrow) represents TECO's search string area. Copy the contents of the search string area into the buffer at the current position of the buffer pointer, leaving the pointer positioned after the last character copied. :G_ Print the contents of the search string buffer on the terminal. ^Q n^QC is identical to nL. The n^Q command returns the number of characters between the buffer pointer and the nth line separator (both positive and negative). This command converts line oriented command argument values into character oriented argument values. Used after an expression. Standard TECO Page C-3 Appendix C C.1.2 STRING BUILD CONSTRUCTS Construct Description Q* Q* indicates that the string stored in the filespec buffer is to be used in the position occupied by the ^EQ* in the search string. Q_ Q_ indicates that the string stored in the search string buffer is to be used in the position occupied by the ^EQ_ in the search string. C.2 SPECIFIC FEATURES OF OS/8 Command Description If used as the first keystroke after TECO's prompt, this command is the same as *Z, that is, it saves the last command string in Q-register Z. This command echoes as *Z and does not have to be followed by an ESCAPE. C.3 SPECIFIC FEATURES OF RSX-11/M, RSX-11/D, IAS, and VAX/VMS Command Description Returns control to the operating system immediately. Equivalent to typing . Standard TECO Page C-4 Appendix C C.4 SPECIFIC FEATURES OF RSTS/E TECO COMMANDS Command Description :EGRTS$ Switch to private default run-time-system. :EGRTS foo$ Switch to RTS "foo". :EGFSS string$ File string scan "string". :EGCCL cmd$ Try "cmd" as a CCL command. :EGRUN file$ Try to run "file". :EGRUN file=xx$ Try to run "file" with "xx" placed in core common. :EGEMT$ Issue a monitor directive. The FIRQB is loaded from Q-registers A through P and the XRB is loaded from Q-registers Q through W. The low byte of the value in Q-register A is the monitor EMT code to issue. If the high byte of the value in Q-reg A is >0 then the text part of Q-reg A is put into the XRB for a 'write' (XRLEN= size of A, XRBC=size of A, XRLOC->A); if Q-reg A high byte is <0 then the text part of Q-reg A is put into the XRB for a 'read' (XRLEN=size of A, XRBC=0, XRLOC->A). Returned value is -1 for success, 0 for unrecognized command, or >0 for the RSTS/E error code. The FIRQB is placed in the numeric part of Q-regs A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P. The XRB is placed in the numeric part of Q-regs Q, R, S, T, U, V, W. 32768+n:W Inserts characters at "dot" until... characters are read (echo off) from the terminal and inserted at "dot" until and according to the microcoded bits in n. 128 => return immediately if no terminal characters 64 => return on any character 32 => don't update screen (i.e., do a -1W) 2 => return on 's Return is always done on control characters (0 through 37 and 177 except ). Returned value has return character code in low byte (0 through 177 or 377 for returned Standard TECO Page C-5 Appendix C immediately); sign bit (value 32768) is set if one or more inserts were done. SWITCHES Switch Description / Same as /B+ Standard TECO Page C-6 Appendix C C.5 SPECIFIC FEATURES OF TOPS-10 Command Description nEM Positions a magtape. You must open the magtape for input with an appropriate ER command before it can be positioned. Exact positioning depends on the value of n, as described below. You must reopen the magtape for output before you can output to it. [TECO-10 only] Value Action 1EM Rewind the currently-selected input magtape to load point. EM is identical to 1EM. 3EM Write an end-of-file record. 6EM Skip ahead one record. 7EM Back up one record. 8EM Skip ahead to logical end of tape (defined by two successive end-of-file marks). Leave the magtape positioned between the two end-of-file marks so that successive output correctly overwrites the second EOF. 9EM Rewind and unload. 11EM Write 3 inches of blank tape. 14EM Advance tape one file. This leaves the tape positioned so that the next item read will be the first record of the next file (or the second end-of-file mark at the logical end-of-tape). 15EM Backspace tape one file. This leaves the tape positioned so that the next item read will be the end-of-file mark preceding the file backspaced over (unless the file is the first file on the tape). ^Q n^QC is identical to nL. This command returns the number of characters between the buffer pointer and the nth line separator (both positive and negative). This command converts line oriented command argument values into character oriented argument values. Used after an expression. Standard TECO Page C-7 Appendix C F0 Pointer position of start of window. Same as 6:W. FZ Pointer position of end of window. FH Same as F0,FZ. FX Software maintained horizontal coordinate of location of cursor on screen (0-origin). Updated by TECO on terminal output. If TECO cannot determine the updated location of the cursor, this value is set to -1. nFX Set value of FX register to n. FY Software maintained vertical coordinate of location of cursor on screen (0-origin). Updated by TECO on terminal output. If TECO cannot determine the updated location of the cursor, this value is set to -1. nFY Set value of FY register to n. FP Equivalent to FY,FX. m,nFP Equivalent to mFYnFX. m,nFF Updates FY and FX registers as if the m,nT command were executed. nFF Assumes that the scope cursor is pointing at the character that is just to the right of the text buffer pointer (the current character). Then this command advances n screen lines and goes to the end of that line and returns that pointer position. nFQq Compares characters beginning at dot with characters beginning at the nth character in Q-register q (0-origin). When a match fails or the match ends, this command moves the pointer to after the last character that matched and returns the index into the Q-register. E=filespec$ Renames the input file. E&filespec$ Run the specified program when TECO exits. Can take a numeric argument which is the run-offset. 0 is the default. m,nE* Does an arbitrary TRMOP to your terminal. [Not available on TOPS-20.] ::Gq Same as :Gq but types literally. ::ER Same as ER but no defaults are used. Standard TECO Page C-8 Appendix C ^Z Closes output file and exits from TECO. ^P Returns current page number. n^P Executes P commands until page n has been reached. n^Y Executes Y commands until page n has been reached. n,m= Same as m=n^T. m,n:^T Does an arbitrary TTCALL. Standard TECO Page D-1 Appendix D APPENDIX D RT-11 OPERATING CHARACERISTICS Startup TECO is started with the .R TECO command. TECO is now immediately ready to accept commands. The text buffer and Q-register areas are empty. The EDIT command .EDIT/TECO filespec is used to edit an already existing file. It is equivalent to .R TECO *EBfilespec$Y$$ For those RT-11 users that will use TECO as the primary editor, a monitor SET command is provided: .SET EDITOR TECO Once this command is issued, the /TECO option on the EDIT command is no longer necessary since the default editor is now TECO. Since this SET command only has affect between system bootstraps, it is recommended that the command be placed in the appropriate startup file (e.g., STARTS.COM). Now, assuming the SET command has been issued, the command .EDIT filespec can be used to edit an already existing file. The standard RT-11 EDIT command options are all available with TECO. .EDIT/CREATE filespec .EDIT/INSPECT filespec .EDIT/OUTPUT:filespec filespec Another option, /EXECUTE, is also available: .EDIT/EXECUTE[:string] filespec The /EXECUTE option causes TECO to process the filespec (assumed .TEC filetype) as a set of TECO commands. If "string" is used, Standard TECO Page D-2 Appendix D the string is placed into TECO's text buffer. If "string" contains only alphanumeric characters, it does not have to be enclosed in quotes. If it is to contain blanks, it must be quoted with single quotes. The equivalent TECO commands would be .R TECO *ERfilespec$YHXZHKIstring$MZ$$ Note the input file remains open and can provide more input to the macro. Startup Conditions The initial value of the ET flag is 0. The initial value of the EU flag is -1. The initial value of the ED flag is 0. File Specification The file access commands ER, EB, and EW accept a file specification in the standard RT-11 format: dev:filename.type in which dev: is a physical device name or a user assigned logical name; if dev: is not specified, the default DK: is assumed. The filename field must be specified in the commands ER, EB, and EW and be a legal RT-11 filename. The type field is a file extension and must be explicitly given if used (there is no default). The EB and EW commands also accept the extended notation for an output file size dev:filename.type[n] The optional [n] specifies the output file size where n is the number of blocks to be allocated. Backup Files The EB command maintains one level of file backup on RT-11. The pre-edited input file name is changed to filename.BAK before the new output file is closed with the original name. Only normal file closing commands (EC, EF, EG, and EX) cause this renaming to happen. If TECO is aborted or the output file is purged by the EK command, the input filename remains unchanged. Note only one .BAK file for a given name is kept; earlier .BAK Standard TECO Page D-3 Appendix D backup files are deleted each time a new backup file is created. A good policy to follow when editing is to close the edited file frequently enough so that an unexpected incident would not cause a substantial loss of work. Files should be backed up regularly. TECO has the power to let an unsuspecting user alter a good file into a completely useless state. The SRCCOM program can be used to verify an editing session. Exit and Go If TECO is exited via the EGstring$ command, the string is passed to the system as the next command to execute. This string may be any valid command or an indirect command file specification. The action taken when the user types depends on what TECO is doing. At command level is a valid input character and has no special meaning. Note though, that if TECO executes as a command from command level, TECO is aborted. If TECO is executing commands or doing I/O, a double will stop the operation and generate the ?XAB error message. A ^T command within a macro can read a as its input character, but another will normally abort the macro. Sometimes it is desireable for a TECO macro to detect when a double was typed. By detecting the double , the macro can exit cleanly back to command level (pop saved Q-registers, restore any flag values, etc.). To do this, the macro sets Bit 15 (Octal 100000, Decimal -32768) of the ET flag. When a double is typed, TECO will automatically turn off Bit 15, but will continue execution of the macro. The macro periodically checks Bit 15 and exits cleanly if it ever goes off. For example: [0 [1 -32768#ETET < ... ET; > 32767&ETET ]1 ]0 REENTER and CLOSE The RT-11 REENTER command may always be used to continue TECO. Its primary differences from running TECO is that when REENTER is used, the text buffer and Q-register areas are unmodified, as opposed to when TECO is run the text buffer and Q-register areas are cleared. The input and output file are always lost upon reentering TECO. If an output file was open Standard TECO Page D-4 Appendix D before reentering TECO, the file will have to be recreated with the appropriate E-command. (Note that the monitor commands GT ON, GT OFF, LOAD, and UNLOAD disallow a REENTER.) The output file is not closed if TECO is aborted. The RT-11 CLOSE command can be used to make the output file permanent, but be aware that the output file will not be complete because of internal buffers that TECO keeps. TECO may be reentered after a CLOSE command. File Recovery TECO can be a useful tool in recovering ASCII files lost on a block replaceable device. TECO allows block replaceable devices to be opened in a non-file structured mode. This gives the user the capability to open a disk and access ASCII data anywhere on it, independent of file boundaries. The command ERdev:$ is used to open the device at which point _ (underscore or backarrow) searches may be used to locate specific ASCII data and transfer it to new output files. Note that files tend to get reproduced, in whole or part, many places on a block replaceable device; be sure to verify that any given text is indeed complete and the correct version. System Crash Recovery TECO and RT-11 are highly reliable, but if during an important edit session a random system failure should occur, the following procedure may help save some or all of the editing. 1. Bootstrap the system 2. Immediately perform a SAVE command to save as much of memory as possible into a file on SY:. The address range form of the SAVE command must be used. The SAVE command will not allow any part of the monitor to be saved, e.g., if you have a 28K system and are running SJ you cannot save 28K but only 26.3K. 3. Perform standard startup procedures, e.g., DATE. 4. Use TECO on the SAVEd file to try and recover useful parts of the edit. VT11 Graphics Support Standard TECO Page D-5 Appendix D If the monitor supports the VT11 graphics processor (GT ON and GT OFF work) TECO will automatically start up in display mode, adjusting to both the size of the display screen and to the presence or absence of the scroller. If the display fails to start with a working VT11, TECO has decided that there is not enough free memory and will not allocate the display file buffer or start the display. See Section 5.15 for a description of the available commands to interact with the display. Various aspects of the display screen become immediately obvious upon seeing them; the text pointer, its position and shape and its position between lines; wrap around of more than 72 characters per line; the scroller interaction and so on. Experiment with a scratch file for more familiarity. EXCEPTIONS RT-11 TECO does not support the following commands that are part of TECO-11 on most other PDP-11 operating systems: 1. Secondary Stream commands (EA, EP, ER$, EW$) 2. Indirect File Input (EI) 3. Wildcards (EN) Standard TECO Page D-6 Appendix D Standard TECO Page E-1 Appendix E APPENDIX E RSTS/E OPERATING CHARACERISTICS Startup TECO is started with the RUN $TECO command. TECO is now immediately ready to accept commands. The text buffer and Q-register areas are empty. The CCL command TECO filespec is used to edit an already existing file. It is equivalent to RUN $TECO *EBfilespec$Y$$ The CCL command TECO filespec1=filespec2 is used to edit existing file "filespec2" into a new file "filespec1". It is equivalent to RUN $TECO *EWfilespec1$ERfilespec2$Y$$ The CCL command TECO/INSPECT filespec is used to inspect an already existing file. It is equivalent to RUN $TECO *ERfilespec$Y$$ The /INSPECT switch may be abbreviated as /IN, /INS, /INSP, etc. The CCL command MAKE filespec is used to create a new file with TECO. It is equivalent to RUN $TECO *EWfilespec$$ Standard TECO Page E-2 Appendix E One more CCL command exists for TECO. It is MUNG filespec --or-- MUNG filespec,text This is equivalent to RUN $TECO *Itext$EIfilespec$$ In other words, the MUNG command will process the filespec as a TECO indirect command file passing an argument of text in the text buffer. This is a convienent way to invoke TECO macros. The TECO and MAKE CCL commands may have the /VTEDIT switch added to automatically invoke the VTEDIT editing macro. $VTEDIT.TEC is loaded into Q-register I and automatically started. The CCL command switches /DETACH and /SIZE:n (or /SIZE:+n) can be used with TECO. If /DETACH is used and the user is privileged, TECO will detach the job before any further processing. If /SIZE:n is used, TECO will pre-expand the text and Q-register storage area to nK. If /SIZE:+n is used, TECO will set the text storage and Q-register storage area to n+3K initially (TECO's default startup size is 3K). Startup Conditions The initial value of the ED flag is always 0. When TECO is initially invoked it will automatically set the ET and EU flags as described below. The ET flag is set to 0 for non-scope terminals without lower case input, to 2 for scope terminals without lower case input, to 4 for non-scope terminals with lower case input, and to 6 for scope terminals with lower case input. In addition, Bit 9 (value 512) will be set if the VT52 "WATCH" feature of TECO is present and your terminal is a VT52 type terminal. Note: The actual ET flag value will be 128, 130, 132, or 134 (Bit 7 on in addition to the above) when TECO initially starts. TECO automatically clears Bit 7 every time it reaches prompt (*) level. The EU flag is set to 0 (flag lower case) for upper case only terminals. It is set to -1 (no flagging) for lower case terminals. File Specification Standard TECO Page E-3 Appendix E The file access commands ER, EB, EW, and EI accept a file specification in the standard RSTS/E format: dev:[p,pn]filename.ext in which dev: is a physical device name or a logical device name; if dev: is not specified, the public structure is assumed. If [p,pn] is not specified, the user's current logged in account is assumed. The filename field must be specified whenever the device name references a file structured device. The .ext field is a file extension and must be explicitly given if used. There is no default extension except for EI commands which default the .ext field to .TEC. The file specification switches /RONLY, /MODE:n, and /CLUSTERSIZE:n can be included in a file specification. TECO automatically opens all disk input files in /RONLY mode. The file size switches /FILESIZE:n and /SIZE:n might leave an output file larger than the amount of data output by TECO. These file size switches are therefore illegal and produce an error if included in a file specification. The EB and EW commands also accept the extended notation for an output file protection code dev:[p,pn]filename.ext The optional specifies the output file protection code. Editing BASIC-PLUS Programs The line feed, carriage return, null combination that signals a continuation line to BASIC-PLUS can cause problems when those files are edited with TECO. To overcome this, TECO has a special "BASIC-PLUS file" edit mode. Simply append a slash to the file specification. dev:[p.pn]filename.ext/ This changes TECO's handling for file input and/or output as follows. On input, TECO will strip off and ignore all nulls (Octal 0, Decimal 0) and carriage returns (Octal 15, Decimal 13). For every line feed (Octal 12, Decimal 10), TECO will automatically insert a carriage return preceeding the line feed. In this way the text buffer has all lines ending with the carriage return, line feed combination. Editing of the text buffer is now easy. On output, TECO will ignore all carriage returns. For every line feed TECO do one of the following: 1) If the character two positions before the line feed was the Standard TECO Page E-4 Appendix E character ampersand (&), TECO will output carriage return and line feed. In other words, the text buffer sequence &, CR, LF will be output unchanged. This is the BASIC-PLUS "EXTEND" mode convention for line continuation. 2) If the character following the line feed is a digit (i.e., the start of a line number) or no characters follow the line feed, TECO will output a carriage return, line feed. 3) If the character following the line feed is not a digit (start continuation line with a tab to ensure this) or the line feed is the last character but a form feed is to be output, TECO will output a line feed, carriage return, null sequence. Editing RSX-11 Run-Time System Generated Files TECO will correctly read RSX-11 Run-Time System generated files of type 1 (fixed length records), type 2 (variable length records), and type 4 (ASCII stream). All types are converted to ASCII stream format in the text buffer. All TECO output files are ASCII stream. Backup Files The EB command maintains one level of file backup on RSTS/E. The pre-edited input file name is changed to filename.BAK before the new output file is closed with the original name. Only normal file closing commands (EC, EF, EG, and EX) cause this renaming to happen. If TECO is aborted or the output file is purged by the EK command, the input filename remains unchanged. Note only one .BAK file for a given name is kept; earlier .BAK backup files are deleted each time a new backup file is created. A good policy to follow when editing is to close the edited file frequently enough so that an unexpected incident would not cause a substantial loss of work. Files should be backed up regularly. TECO has the power to let an unsuspecting user alter a good file into a completely useless state. The FILCOM program can be used to verify an editing session. Wild Card Lookup The EN command will process wild card lookups on RSTS/E. To preset the wild card lookup file specification, use the standard RSTS/E format dev:[p,pn]filename.ext Standard TECO Page E-5 Appendix E The device name must reference a file structured disk device, be the public structure (SY:), or be omitted which defaults to the public structure. The [p,pn] field cannot be wild. It defaults to the user's current logged in account. The filename field must be specified and can be explicit, fully wild (i.e., *), or partially wild (i.e., containing one or more ?'s). If the .ext field is omitted, only files with no extension will be looked for. Otherwise, the extension field can be explicit, fully wild (*), or partially wild (?'s). Exit and Go If TECO is exited via the EGstring$ command, the "string" is executed as a RSTS/E CCL command after the input and output file(s) are closed. For information on :EG see Appendix C.4. The action taken when the user types depends on what TECO is doing. If TECO is executing commands, the ?XAB error occurs. If TECO is in the midst of doing I/O, the error "?ERR ?Programmable ^C trap" occurs. If TECO is at command level or asking for a character with the ^T command, TECO simply restarts and reprompts its asterisk. If two s are typed to TECO when it is at command level, it will exit. Sometimes it is desireable for a TECO macro to detect when a was typed. By detecting the , the macro can exit cleanly back to command level (pop saved Q-registers, restore any flag values, etc.). To do this, the macro sets Bit 15 (Octal 100000, Decimal -32768) of the ET flag. When a is typed, TECO will automatically turn off Bit 15, but will continue execution of the macro. The macro periodically checks Bit 15 and exits cleanly if it ever goes off. For example: [0 [1 -32768#ETET < ... ET; > 32767&ETET ]1 ]0 If Bit 15 is on and TECO is waiting for a response to a ^T command and the user types a , TECO will turn off Bit 15 and return an ASCII code of 3 (the code for ). ET Flag Handling Standard TECO Page E-6 Appendix E TECO will automatically turn off the following bits in the ET flag on every error: 1's bit (image output), 8's bit (no echo on ^T), 16's bit (cancel ^O), 32's bit (no stall on ^T), and the high-order bit (^C trap). In addition, TECO always turns off Bit 7 (exit on error, etc.) every time TECO reaches prompt (*) level. Bit 6 (detach) is handled specially by TECO. Every time the ET flag is read (used as a numeric value), TECO ensures that Bit 6 is on if the job is attached or off if the job is detached. This allows a TECO macro to check for "detachedness". If a non-privileged user attempts to set Bit 6, the request is ignored and Bit 6 will read back as a 0 (assuming the job is attached). When a privileged user sets Bit 6, the job will become detached. Further reading of Bit 6 will return a 1 to indicate the detached condition. Installing TECO The following commands will install TECO on your RSTS/E V06C system. (Note: dev: is your distribution medium.) RUN $PIP.SAV *[0,1]*.*<60>=dev:[0,1]TECO.RTS *[0,1]*.*<60>/MO:16=[0,1]TECO.RTS *$*.*<104>=dev:$TECO.TEC *$*.*<104>=dev:$VT52.TEC *$*.*<104>=dev:$TYPE.TEC *^Z RUN $UTILTY < UTILTY's header line > ? NAME TECO=$TECO.TEC ? NAME TECO=$VT52.TEC ? NAME TECO=$TYPE.TEC ? ^Z Inclusion of TECO on System Startup The following commands will include TECO on your RSTS/E V06C system at system startup time. RUN $UTILTY < UTILTY's header line > ? ADD TECO ? CCL MAK-E=$TECO.TEC;[PRIV ]n ? CCL MU-NG=$TECO.TEC;[PRIV ]n ? CCL TE-CO=$TECO.TEC;[PRIV ]n ? CCL TY-PE=$TYPE.TEC;n ? ^Z Standard TECO Page E-7 Appendix E The n above is a memory usage limit. If n is 0 then the TECO will expand its memory on demand up to the user's memory limit. If n is non-zero then TECO will not expand its memory over nK. For most installations, n will be 0 for MAKE, MUNG, and TECO. For TYPE, n is usually 8. If PRIV is included and TECO.TEC's protection code is changed to <232>, TECO will expand its memory beyond the user's private memory limit (but never beyond the limit set by n if any). Most installations will not include PRIV in their CCL definitions. RSTS/E TECO I/O handling changes If running under RSTS/E V7.0: a) Tentative files are used b) Wild card PPN's are available with EN c) No supersede mode is recognized The following switches are recognized with EB, ER, and EW: /MO:n RSTS/E file open mode /CL:n RSTS/E file cluster size (means block size on ANSI magtapes) /B binary input/output mode; all data is read/written as unfiltered 8-bit / same as /B+ /B+ Old BASIC-PLUS source file processing; correctly reads/writes line feed style continuation lines /B2 same as /8 /n BASIC-PLUS-2 source file processing; correctly reads/writes & style continuation lines; the & is placed in column n The following sequential disk file formats are handled: ASCII stream if no file attributes of if ASCII stream (R.STM) attribute (this is the default processing mode) Fixed if fixed (R.FIX) attribute Variable if variable (R.VAR) attribute Variable w/ fix if variable with fixed control (R.VFC) attribute Standard TECO Page E-8 Appendix E Fortran carriage control (FD.FTN) is converted for R.FIX, R.VAR, R.VFC Implied carriage control (FD.CR) is added for R.FIX, R.VAR, R.VFC Print format control (FD.PRN) is converted for R.VFC No block spanning (FD.BLK) is recognized for R.FIX, R.VAR, R.VFC The following ANSI magtape file formats are handled: Fixed (format "F") Variable (format "D") ASCII stream (format "U") (this is the default processing mode) Fortran carriage control (modifier "A"??) is converted Implied carriage control (modifier " "??) is added Embedded carriage control (modifier "M") is recognized (this is the default) On output, if the magtape is an ANSI magtape, the format written is variable (format "D") with implied carriage control (modifier " ") and a default block size of 2048 bytes per block (modifyable by /CL:n) Standard TECO Page F-1 Appendix F APPENDIX F RSX-11 OPERATING CHARACERISTICS Startup RSX-11 systems support all of the standard TECO invocation commands, namely TECO TECO filespec TECO filespec=filespec MAKE filespec MUNG filespec MUNG filespec,text If any of these commands are not recognized by the system, check with your system manager to see that TECO is properly installed. TECO macros may also be invoked with the command TECO @filespec It is exactly equivalent to MUNG filespec In systems supporting dynamic task expansion, TECO will expand its buffer space as necessary. Also, TECO'S buffer space may be explicitly allocated in the startup command RUN $TEC/INC=n Initialization TECO searches for the TECO.INI startup file in the current default device and directory. TECO's memory, in which a plain TECO command edits the file last edited with a TECO filespec or a MAKE filespec command, is implemented with a file named TECF00.TMP, also stored in the current default device and directory. The initial value of the ED flag is always 1. When TECO is initially invoked it will automatically set the ET and EU flags according to the user's terminal characteristics. If the terminal supports CRT style rubouts, then bit 1 of the ET flag is set to do the same in TECO. If the terminal supports lower case type in, then bit 2 of the ET flag is set and the EU flag is set to -1 to turn off case flagging. If the terminal is a CRT type terminal and the version of TECO includes the screen Standard TECO Page F-2 Appendix F support package, then bit 9 of the ET flag is set. While the command line is being processed, bit 7 of the ET flag is also set to cause TECO to exit should any errors occurr. ET bit 7 is cleared every time TECO reaches prompt (*) level. File Specification The file access commands ER, EB, EW, and EI accept a file specification in the standard RSX-11 format: dev:[p,pn]filename.typ;version in which dev: is a physical device name or a logical device name; if dev: is not specified, SY: is assumed. If [p,pn] is not specified, the user's current default directory is assumed. The filename field must be specified whenever the device name references a file structured device. The typ field is a file type and must be explicitly given if used. There is no default type except for EI commands which default the .typ field to .TEC. The switch /RW may be applied to any file specification in an ER, EW, and EI command. If the file specification references a magtape, the tape is rewound before the file is opened. Note that for output files, this has the effect of zeroing the tape. The /RW switch is ignored for all other device types. The presence of version numbers in Files-11 causes file processing to behave slightly differently under RSX-11 than under other operating systems. For example, no .BAK files are used; each execution of an EB command simply produces a new version of the file. Thus a user may retain any level of backup he feels to be comfortable. It also means that one must occasionally delete obsolete files to avoid cluttering the disk. Thus the command EBname.typ;version$ is equivalent to the commands ERname.typ;version$EWname.typ;0$ The EW command also creates a new version (one higher than the current highest) if no version number is given. If an explicit version number is given, then that number is used, and if another file of the same name, type, and version previously existed, it is superseded without warning. (See use of the EP and EK commands below.) In reading files, version numbers behave the same as in other RSX-11 utilities: the default is the highest version. This leads to a problem in re-opening the input file while a file is being edited with EB. Since the output file is already created and in the directory, the input file is no longer the highest version. One may deduce the version number of the input Standard TECO Page F-3 Appendix F file by doing a G* (returning the file string of the output file) and subtracting one from that version number. In symmetry with the EB command, the EK command functions by simply deleting the current output file. Note, however, that a supersede (EW of same name, type, and version) is not undone - the file is already deleted! The EP and EA commands, while simulating two channels each with an open file for each of input and output, in fact only keep one file open for each to conserve buffer space. This means that they are only useful for disk files. Also, it means that if one opens a file and then supersedes it, one should not switch the input channel away from it with an EP or ER$ command, since it will not be possible to open the file again. Wild Card Lookup The EN command will process wild card lookups on RSX-11. To preset the wild card lookup file specification, use the standard RSX-11 format dev:[p,pn]filename.typ;version The device name must reference a file structured disk device or magtape. All other fields of the file specification may be fully wild (*), including either or both halves of the directory. The version number may be explicit, wild, or default. As with the other file specification commands, there is no default file type. Exiting from TECO The normal method of exiting from TECO is with the EX command. This copies the remaining input file to the output file, closes all files and exits. To protect against accidental loss of text typed in, the EX command will not allow TECO to exit if there is text in the buffer and no open output file. To exit after just looking at a file, one must use the sequence HKEX. The EG command is identical in action to the EX command, since RSX-11 has no facility for passing control from one program to another. The action taken when the user types depends on what TECO is doing. If TECO is executing commands, or is awaiting type-in for the ^T command, the ?XAB error occurs. Standard TECO Page F-4 Appendix F If TECO is at command level, typing cancels the command string currently being typed and returns TECO to its prompt. Two consecutive characters will cause an instant HKEKEX exit. Sometimes it is desireable for a TECO macro to detect when a was typed. By detecting the , the macro can exit cleanly back to command level (pop saved Q-registers, restore any flag values, etc.). To do this, the macro sets Bit 15 (Octal 100000, Decimal -32768) of the ET flag. When a is typed, TECO will automatically turn off Bit 15, but will continue execution of the macro. The macro periodically checks Bit 15 and exits cleanly if it ever goes off. For example: [0 [1 -32768#ETET < ... ET; > 32767&ETET ]1 ]0 Setting the intercept bit in the ET flag must be done with some care; if the bit is set inside a command loop which does not check it, it will be impossible for the user to abort the loop. The only remedy for this situation is to abort TECO from another terminal. ET Flag Handling TECO will automatically turn off the following bits in the ET flag on every error: Bit 0 (image output), Bit 3 (no echo on ^T), Bit 4 (cancel ^O), Bit 5 (no stall on ^T), and Bit 15 (^C trap). In addition, TECO always turns off Bit 7 (exit on error, etc.) every time is reaches prompt (*) level. Bit 6 (the detach flag) controls TECO'S treatment of the terminal. Normally, TECO keeps the terminal attached to gain control of interrupts. Setting bit 6 of the ET flag causes TECO to run with the terminal detached. All commands function normally, except that typing causes the MCR to be activated, allowing other tasks to be run from the same terminal concurrently with TECO. It is, of course, the user's problem to sort out the confusion that will arise if both TECO and another task request input from the terminal at the same time. Standard TECO Page F-5 Appendix F File Record Format Files-11 files are record structured, while TECO'S text buffer is ASCII stream. Thus TECO must make format conversions when reading and writing files. The conversion depends on the record attributes of the file. While reading a file, the records are packed into the buffer. If the file is implied carriage control (the standard RSX-11 source format) or Fortran carriage control, TECO inserts a carriage return and line feed after each record to make each record appear as a line of text in the buffer. The one exception to this processing is a record containing just a form feed. This is interpreted as an end of page mark; it stops the read operation but is not entered in the buffer. If the input file has no carriage control (also called internal carriage control), TECO simply packs the records together in the text buffer. Print Format files (FD.PRN) can be read (but not EI'd or written). On output, TECO scans the text buffer for carriage return / line feed sequences. Each carriage return / line feed delimits the end of an output record. If the output file is implied or Fortran carriage control, the carriage return and line feed are not output with the record; if the file is internal carriage control, they are. Form feed characters in the buffer are always output as a single character record. Note that solitary carriage returns and line feeds, and line feed / carriage return sequences do not delimit records, but remain embedded in the records being output. Switches may be applied to the input and output files to control their carriage control attributes. The switch /CR forces implied carriage control; /-CR forces no (internal) carriage control; /FT forces Fortran carriage control. When a carriage control switch is applied to an input file, the file is read as if it had that attribute; when the switch is applied to an output file, the file is written with that attribute. Applying a switch to an EB file specification causes the switch to apply to both input and output files. When an output file is created, its carriage control attributes are defaulted to those of the currently open input file as follows: Input Output implied implied none implied Fortran Fortran Standard TECO Page F-6 Appendix F Files read with the EI command have their record attributes interpreted in the same manner. This leads to an unexpected side effect with EI files containing an entire command. The last record of the file presumably contains as its last characters the two alt modes which initiate execution of the macro. If the file is implied carriage control, however, there are also the final carriage return / line feed belonging to the last record, which remain in the type in buffer while the macro executes. If the macro attempts to receive input with the command, the carriage return / line feed will be the first two characters read. Alternatively, if the macro does no type in, the carriage return / line feed will be read by TECO as the first two characters of the next command. Then no asterisk (*) will appear as the prompt for the next command. The remedy for both cases is for the macro to execute an EI$ command early on. This causes the remainder of the indirect file to be discarded and further input to be read from the terminal. Command Line Processing The mechanism used to process the command line in RSX-11 TECO is designed to allow sophisticated TECO users the greatest flexibility in customizing TECO for their own use. It functions as follows: The initialization routine places the original MCR command line (if any) into the filename buffer. It copies into the text buffer the text of a TECO macro that will be used to interpret the command line. Then it starts up TECO with the command HXY HKG* HXZ HK :EITECO$$ in the type in buffer. This loads the command line into Q-register Z and the macro into Q-register Y. It then executes the file named TECO.TEC located in the user's default directory, if it exists. After the user's TECO.TEC, and any files it might link to with EI, have been executed, TECO executes the command MY$$, thus executing the macro to interpret the command line and open the files requested. The TECO.TEC mechanism should not be used for simple initialization; the standard TECO.INI facility should suffice for that. The alternate TECO.TEC facility is provided for the sophisticated user who wants his own command processing and thus wishes to usurp control from the normal initialization. Standard TECO Page F-7 Appendix F If an EI$ command (to close the indirect command file) is executed during the processing of a user's TECO.TEC startup file, the final MY$$ which causes processing of the command line is not executed. This results from the fact that the MY$$ normally appears in TECO's type in after all command files have been processed. Executing the EI$ command causes all "type ahead" to be discarded to allow a TECO command file to prompt and read input from the terminal (and not read extraneous type ahead). It is assumed that a TECO startup file that executes EI$ and reads input from the terminal will want to manage the rest of TECO's startup. If it still wants to process the command line, it must issue the MY itself. Installing TECO The first step in installing TECO is to copy the files from the distribution medium into an available directory on the system disk. TECO distributed on Magtape or DECtape is in DOS format; floppy disks are in RT-11 format. The kit should be read with FLX with an appropriate command of the form FLX SY:=MT:[1,1]*.* or FLX SY:=DX:*.*/RT The kit contains an executable TEC.TSK file which is suitable for most fully configured RSX-11M systems. To make link time changes to TECO, one must edit the TKB command file TECBLD.CMD and TECBLD.ODL. The files are commented to indicate what options are available. One must then build TECO with the command TKB @TECBLD Users with unmapped RSX-11M systems will need to edit the TKB command file to alter the PARTITION directive to fit their system. RSX-11M users should also note that the size of TECO with the screen package is about 11.5K words, excluding its text buffer. Thus, TECO requires a minimum partition of about 16K words to be useful. Once task built, TECO needs to be installed under three names to make all of the commands available: INS TEC default name is ...TEC INS TEC/TASK=...MAK for the MAKE command INS TEC/TASK=...MUN for the MUNG command In IAS, TECO is installed instead under the task names $$$TEC, $$$MAK, and $$$MUN to implement the three commands. Standard TECO Page F-8 Appendix F TECO makes use of features which are optional in some systems, such as dynamic task expansion, the read with special terminators terminal function in RSX-11M (i.e., TECO mode), and unsolicited character AST's in IAS. It is also designed to use the type-ahead feature in the new terminal driver supplied with RSX-11M V3.2 and RSX-11M+; while it will function correctly with the old terminal driver, the keypad editor macros will not work well at all because of the old terminal driver's inability to keep up with escape sequences. TECO may be reconfigured to do without some of these features to allow it to run on subset or older systems; instructions on this are to be found in the assembly and TKB command files, and in the assembly prefix file TECPRE.MAC. The following new switch is recognized with EB, ER, and EW: /B2 BASIC-PLUS-2 source file processing; correctly reads/writes & style continuation lines. On input, all lines ending with & have that & and, then, all trailing spaces and tabs removed. On output, any line with a following line that doesn't start with a digit is assumed to be a continuation line; it is suffixed with one space and a &. This algorithm allows you to correctly edit well formed BASIC-PLUS-2 source files without regard having to worry about &'s. Three Control/Z's in a row will cause TECO to exit. This helps the termination of TECO in batch streams... There exists a global patch location (TE.INI) which governs TECO's startup handling. The bits to patch there are described in the comments of the TECO.INI file (the bit encoded flag bits). Specifically, bit 12 (4096(10), 10000(8)) says to not try to find the TECO.INI file (i.e., disable private initialization) and bit 2 (4(10), 4(8)) says to not use or TECO's memory file (i.e., disable memory). Standard TECO Page G-1 Appendix G APPENDIX G VAX/VMS OPERATING CHARACERISTICS TECO runs in compatibility mode under VAX/VMS; as such, its behavior is almost identical to that in RSX-11M. This appendix describes only the differences from RSX-11M. Startup All of the normal TECO invocation commands may be used. The RUN $TEC/INC=n command is not available, nor is it necessary since dynamic task expansion is supported. Initialization TECO looks for your TECO.INI and locates its TECF00.TMP file in your top level directory (i.e., the directory reached by traversing up your current default directory string toward the MFD). File Specification All file specifiers are subject to the VAX/VMS file specifier rules; logical names and multi-level directories are properly handled. Remote network file access is not available. In wild card file name processing, the file string supplied in the EN command may contain a directory spec of the form [*], which is equivalent to [*,*] and matches all directories. Wild carding through subdirectories is not supported. Control-C and Control-Y TECO handles in the same way as it does on RSX-11M. is not handled at all and wil result in trapping to the command interpreter. Should you accidentally type , immediately type CONTINUE in response to the DCL prompt to resume editing. Installing TECO The VAX/VMS TECO kit contains a fully configured TEC.EXE file that is ready to run; simply copy it into SYS$SYSTEM:. The macros supplied in the kit should be copied to SYS$LIBRARY:; the documentation files should be placed in SYS$HELP:. Standard TECO Page G-2 Appendix G Since the TECO commands are not part of the VAX/VMS command interpreter, each user must define the commands in his LOGIN.COM file. The following commands will define the three normal TECO invocation commands: $ TECO :== $TEC TECO $ MAKE :== $TEC MAKE $ MUNG :== $TEC MUNG One may include command switches in the command definitions. For example, one can define a command to invoke TECO with VTEDIT as follows: $ VTECO :== $TEC TECO /VTEDIT Standard TECO Page H-1 Appendix H APPENDIX H OS/8 OPERATING CHARACERISTICS H.1 Startup TECO is started with the .R TECO command. TECO is now immediately ready to accept commands. The text buffer and Q-register areas are empty. The TECO command .TECO filespec is used to edit an already existing file. It is equivalent to .R TECO *EBfilespec$Y$$ OS/8 "remembers" the filespec as the name of the last file that has been edited. The MAKE command .MAKE filespec is used to create a new file. It is equivalent to .R TECO *EWfilespec$$ OS/8 "remembers" the filespec as the name of the last file that was edited. The command .TECO filespec1=filespec2 is used to edit filespec2 into filespec1. That is, filespec2 is opened as the input file, and filespec1 is created as the output file. It is equivalent to .R TECO *ERfilespec2$EWfilespec1$Y$$ OS/8 "remembers" the fielspec1 as the name of the last file that was edited. Standard TECO Page H-2 Appendix H The command .TECO with no arguments, causes CCL to execute the command .TECO filespec where filespec was the file that was previously remembered as the last file to be edited. The system purposely does not remember filenames from one day to the next, but it will remember names across bootstraps. The command .MUNG filespec executes the specified TECO program. The default extension is .TEC . This is equivalent to the sequence: .R TECO *ERfilespec$YHXYHKMY$$ Another format of this command is .MUNG filespec,argument which is used to pass an argument to the TECO program to control its action. This is equivalent to the sequence: .R TECO *ERfilespec$YHXYHKIargument$MY$$ The argument may be the name of a file that the TECO program is to mung, or it may be a command to the program to specify what action to take, or whatever. It is up to the TECO program to decode this argument (which is left in the text buffer) and take appropriate action. A TECO program executed via the MUNG command must never destroy the text storage area of Q-register Y and expect to ever see the light of day again. Note the input file remains open and can provide more input to the macro. H.2 Startup Conditions The initial value of the EU flag is 0 if the CCL command SET TTY NO SCOPE had been previously issued, and is -1 if the CCL command SET TTY SCOPE had previously been issued. Standard TECO Page H-3 Appendix H The initial value of the ET flag is as follows: Bit value Initial value 1 0 2 0 (1 if terminal is a scope) 4 0 8 0 16 0 32 0 64 0 128 1 (TECO's prompt sets this to 0) 256 0 512 0 (1 if VT support is present) 1024 0 (1 if VR12 support is present) 2048 0 The initial value of the ED flag is 1. H.3 File Specification The file access commands ER, EB, and EW accept a file specification in the standard OS/8 format: dev:filename.type in which dev: is a physical device name or a user assigned logical name; if dev: is not specified, the default DSK: is assumed. The filename field must be specified in the commands ER, EB, and EW and be a legal OS/8 filename. The type field is a file extension and must be explicitly given if used (there is no default). Any characters after the second will be ignored, thus the filespecs FOO.TEC and FOO.TE are equivalent. The EB and EW commands do not accept the extended notation for an output file size dev:filename.type[n] specifying an output size allocation. H.5 Backup Files The EB command maintains one level of file backup on OS/8. The pre-edited input file name is changed to filename.BK before the new output file is closed with the original name. Only normal file closing commands (EC, EF, EG, and EX) cause this renaming to happen. If TECO is aborted or the output file is purged by the EK command, the input filename remains unchanged. Note only one .BK file for a given name is kept; earlier .BK Standard TECO Page H-4 Appendix H backup files are deleted each time a new backup file is created. A good policy to follow when editing is to close the edited file frequently enough so that an unexpected incident would not cause a substantial loss of work. Files should be backed up regularly. TECO has the power to let an unsuspecting user alter a good file into a completely useless state. The SRCCOM program can be used to verify an editing session. H.6 Exit and Go If TECO is exited via the EGstring$ command, the string is passed to the system as the next command to execute. This string may be any valid command or an indirect command file specification. The command may be either a KBM or a CCL command. This command is especially useful while running under BATCH. If TECO is exited via the EG$ command, then OS/8 will re-execute the last explicit compile-class command that was executed that day. The commands that are considered to be compile-class commands are: COMPILE file LOAD file EXECUTE file LINK file MACRO file. This feature, combined with OS/8's other remembering features, minimizes the number of keystrokes necessary to do normal program development. The programmer does not have to constantly type in the name of the file he is working with. A typical debugging session would look like this: .MAKE FOO.MAC *!type in assembly language file to be executed! *EX$$ .EXECUTE FOO (get error messages) .TECO *!fix bugs! *EG$$ !re-compile and execute program! (watch program work or repeat process) H.7 The action taken when the user types depends on what TECO is doing. At command level is an immediate action command. If typed as the very first character in a command string (not necessarily the first keystroke) it aborts TECO and returns to the keyboard monitor. If this was done accidentally, TECO may be restarted (at your own risk) by using Standard TECO Page H-5 Appendix H ODT to branch to location 207 in your program's image. If is typed int he middle of entering a command string, then the ?XAB error message is given and TECO reprompts with its asterisk. Note that if TECO executes as a command from command level, TECO is aborted. If TECO executes a command from within a macro, TECO is also aborted. If a is typed while TECO is running, or while TECO is typing on the terminal, or while an error message is printing, then the ?XAB error message is given and TECO reprompts with its asterisk. Similarly, if is typed while TECO is waiting for input because of a T command. Note that if TECO is performing I/O using non-system handlers, the non-system handler may intercept the and abort back to the keyboard monitor. In such a case, you may attempt to re-enter TECO, however, part of your file has been lost and good luck in attempting to issue an EF command. Manually resetting the value of Z might recover your data. If TECO is executing commands or doing I/O, e will stop the operation and generate the ?XAB error message. Sometimes it is desireable for a TECO macro to detect when a was typed. By detecting the , the macro can exit cleanly back to command level (restore any flag values, etc.). To do this, the macro sets Bit 0 (Octal 4000, Decimal 2048) of the ET flag. When a is typed, TECO will automatically turn off Bit 0, but will continue execution of the macro. The macro periodically checks Bit 0 and exits cleanly if it ever goes off. If the trap bit is on, then the T can read a typed at the terminal. It has an ASCII value of 3. H.8 File Recovery TECO can be a useful tool in recovering ASCII files lost on a block replaceable device. TECO allows non-file-structured devices to be opened in a non-file structured mode. This gives the user the capability to open a disk and access ASCII data anywhere on it, independent of file boundaries. To do this, you must issue a command of the form .SET dev: NOFILES to the monitor to make it think that your disk is non-file-structured. The command ERdev:$ is used to open the device at which point _ (underscore or backarrow) searches may be used to locate specific ASCII data and transfer it to new output files. Note that files tend to get reproduced, in whole or part, many places on a block replaceable device; be sure to verify that any given text is indeed complete Standard TECO Page H-6 Appendix H and the correct version. If the disk's directory has not been clobbered (or if you are willing to create a new one), then it is not necessary to turn the disk into a non-file-structured device. Merely open up a file early on the disk for input and read through end-of-files until you locate the lost file. To read through end-of-files, you must use the /S switch on an ER, EB, or EW command. For example, the command ERFOO.MAC/S$ will open the file FOO.MA for input and put tECO into "SUPERTECO" mode. In this mode, TECO will not treat a found in a file as an end-of-file character. Instead, will be treated like any other character. It is not a line terminator or a page terminator. This mode continues until an ER, EW, or EB command is issued without a /S switch. H.9 VR12 Graphics Support If TECO is run on a PDP-12, TECO will automatically start up in display mode, adjusting to both the size of the display screen and to the presence or absence of the scroller. On a PDP-12, TECO only permits one-page input and output handlers. See Section 5.15 for a description of the available commands to interact with the display. Various aspects of the display screen become immediately obvious upon seeing them; the text pointer, its position and shape and its position between lines; wrap around of more than 72 characters per line, and so on. Experiment with a scratch file for more familiarity. H.10 EXCEPTIONS TECO-8 does not support the following commands which are described in this manual: 1. Secondary streams (EP, EA, ER$, EW$) 2. Auxiliary command streams (EI) 3. Wildcards (EN) 4. Zeroing of directories (EZ) Standard TECO Page H-7 Appendix H 5. Magtape commands (EM) 6. View command (V) 7. Bounded searches 8. Anchored searches 9. Search verification (ES) 10. Command verification (EV) 11. Backward searches 12. Extended string build or match constructs (^Ex) The following incompatibilities exist between TECO-8 and Standard TECO: 1. In octal mode, the digits 8 and 9 are not treated as errors when occurring in a numeric string. 2. The *q immediate action command is not implemented. Instead, the immediate action command * has the same effect as *Z of the standard. (The immediate mode command ^S is still accepted for compatibility with OS/8 TECO V5.) H.11 Chaining to TECO A user program may chain to TECO passing it a command to be executed. There are two formats that such a command may take. Format 1 (the TECO command format) passes TECO a valid TECO command to be executed. This TECO command is placed in a buffer starting at location 17600, one 7-bit ASCII character per word. A negative word represents a pointer to a continuation buffer in field 1. There may be any number of continuation buffers, but they must all begin above location 4000 in field 1. Since TECO clobbers most of field 1, these buffers must in fact start above location 7400. TECO will never load into page 7400 of field 1. The buffer ends with a fullword 0. Format 2 (the CCL command format) passes TECO a CCL command to be parsed and executed. Such a command usually begins with the words TECO, MAKE, or MUNG, but is not limited to these words. Such a CCL command is placed in a buffer starting at location 17601, one 7-bit ASCII character per word. Location 17600 must be a fullword 0 to specify that this format is being used. A negative word in the buffer represents a pointer to a continuation buffer in field 1 as described above. The buffer ends with a fullword 0. If this format is used, the passed CCL command will be parsed and executed by TECO.TEC as described Standard TECO Page H-8 Appendix H below. A user may write his own TECO.TEC, thus implementing his own CCL commands. There is no limit to the possiblities, other than the user's imagination. H.12 User Initialization If a user has a file called TECO.INI on SYS:, then when TECO starts up (via a CCL command, it will execute the contents of this file (as a TECO macro). This file must contain a valid TECO program (which will execute out of Q-register W). God help you if you have any errors in this program. This start-up file must not modify itself (Q-register W) and must not modify the contents of Q-register V. It should not indiscriminately modify the contents of Q-register Z or the text buffer. TECO.INI will be executed before TECO opens any files. That is, if TECO was invoked via a MAKE command, TECO.INI will be executed before the EW command (for the MAKE) is executed. At this point, the text buffer will contain a copy of the CCL command that invoked TECO (assuming your monitor has TECO.TEC support). However, TECO has not as yet parsed this line. The user may examine this line for himself, and modify it, but you had better know what you are doing (and do it right!). TECO.TEC will parse the contents of the text buffer at the conclusion of execution of TECO.TEC. If your monitor does not have TECO.TEC support, or if a user program chained to TECO passing it a TECO command (rather than a CCL command), then the initial TECO command will be in Q-register Z when TECO.INI gets control. That command has not as yet been executed. The initialization file may examine the contents of Q-register Z to determine what TECO command will be executed and proceed accordingly. It may also modify the contents of Q-register Z (but you better know what you are doing). In this case, TECO.INI is started up via the sequence @:ER/SYS:TECO.INI/"SYHXWHK @^UZ^@teco command^@ MW+0ES.,.XWMZES"N0ESMX'$$ which loads TECO.INI into Q-register W, loads the chain argument consisting of an appropriate teco command into Q-register Z, and temporarily stores the value returned by TECO.INI in the search verification flag (this feature may change in a subsequent release). Q-register W and ES are cleared before the post-processing command in Q-register X is executed. Note that the chain argument may not contain any embedded nulls. H.13 RETURNED VALUES FROM TECO.INI TECO.INI may also return a value. If your monitor does not support TECO.TEC, then only two values are permitted. Returning a 0 (or not returning anything) is the normal sequence of events. Standard TECO Page H-9 Appendix H Returning a 1 means that TECO should execute the contents of Q-register X (via an MX command) after it executes the initial TECO command (in Q-register Z). TECO.INI may set up Q-register X with the appropriate post-processing commands. A typical use of this feature would be to have TECO.INI load up Q-register I with an editing macro and then put an "MI" command in Q-register X for subsequent execution. If your monitor does have TECO.TEC support, then TECO.TEC can support additional returned values. It is recommended that TECO.TEC support the returned values of 0 and 1 as above, but in addition, it may support additional values determined by the user. Note that TECO.INI is not invoked if TECO is started with a RUN or R command. H.14 TECO.TEC Support If the version of CCL you are using to invoke TECO supports TECO.TEC, then it will chain to TECO with a 0 at location 17600 and will pass TECO the invokig CCL command (beginning at location 17601). If TECO is invoked in this manner, it will parse this CCL command by executing the TECO command line parser macro stored in SYS:TECO.TEC. This macro can be modified by the user to parse switches or do any special processing that is desired. TECO.TEC is started up via the command @I^@ccl command^@:ER/SYS:TECO.TEC/"F^ACan't find SYS:TECO.TEC ^A^C^CA.,ZXV.,ZKMV.,.XV$$ which puts your CCL command in the text buffer and then loads (the first page of) TECO.TEC into Q-register V. TECO.TEC is then executed with the MV command and then Q-register V is cleared. It is the responsibility of TECO.TEC to parse the command line in the text buffer and do the appropriate processing and clean-up. It is also the responsibility of TECO.TEC to execute a user's start-up file (TECO.INI) if one is present. Note that TECO.TEC is not invoked if TECO is started via a RUN or R command. Also note, that the CCL command may not contain any embedded nulls. H.15 Overlays The key to writing fast TECO programs lies in understanding TECO-8's overlay structure. If TECO-8 is run in 16K or more (20K or more if VT support is present), then the overlays will be memory-resident rather than disk-resident. Although this is much faster than swapping from the disk, swapping from memory still involves some overhead, so it would be wise to structure your TECO program to minimize the number of swaps necessary. The overlay structure is designed so that the minimal number of swaps will be required unless obscure TECO features are used. There are five overlays to TECO: Standard TECO Page H-10 Appendix H 1. The I/O-overlay. This overlay handles file opening and is initially resident. Thus no swapping is necessary to do in initial ER, EW, or EB. 2. The Q-overlay. This overlay contains most of the frequently used conditional commands and branching commands. It is intended that this overlay swap in once and remain in memory until TECO is exited. 3. The X-overlay. This is the exit overlay and handles commands needed only when TECO is exiting, such as EX, EF, EC, and EG. It is intended that this overlay will swap in only once when you are ready to leave TECO. 4. The F-overlay. This overlay contains the flag commands and other little-used commands. It is intended that this overlay be not used at all, or if it is used, it will be used so infrequently that it will not slow down system performance. 5. The E-overlay. This is the error overlay. It is swapped in only when an error occurs. It is intended that this overlay never be swapped in. To write efficient TECO code, the user must know exactly which commands are handled by which overlay. This information is summarized below. Overlay Commands I-overlay ERfile$, EWfile$, EBfile$, :ERfile$, :EBfile$ Q-overlay Otag$, n"Xthen|else', n;, search;, n<...>, <...> X-overlay EC, EG$, EGcmd$, EF, EK, EX, *q, ?, nEJ, n^_, V, ^B, ^E, ^F, ^L, ^N, ^Uqtext$ F-overlay ED, EH, EO, ES, ET, EU, ^D, ^O, ,break \, n\, n=, n==, n:=, n:==, | Several things are immediately obvious. The command 0TT should always be preferred tot he V command. ELSE clauses should be avoided. (In future releases, we will try to move the processing of the | command into overlay Q.) The commands \ and = should be used as infrequently as possible from within long-running macros. Xq is preferred to ^Uq to load up a Q-register. -n-1 is preferred to n^_ to take a one's complement. Radix changes should be avoided. Flags, such as ET and ED, should be set once at the beginning of a macro, and then not fiddled with if at all possible. H.16 Installation Instructions Standard TECO Page H-11 Appendix H The source of TECO consists of the following modules: TECO.MAC Main module TECINI.MAC Initialization module TECTBL.MAC Tables TECDEF.MAC Global definitions TECO12.MAC VR12 support TECOVT.MAC VT support TECOVI.MAC I/O-overlay TECOVQ.MAC Q-overlay TECOVX.MAC X-overlay TECOVF.MAC F-overlay TECERR.MAC E-overlay and error processor TECSRH.MAC Search processor TECNUM.MAC Arithmetic processor Each of these modules should be assembled (using MACREL V2 or later). This can be accomplished via the command .MAC TEC???.MAC if your monitor supports wildcards in compile-class commands. The resulting relocatable modules are then linked together (using LINK V2 or later) to produce the executable TECO.SV image which should be put on SYS: (but it may reside on any device). If your monitor supports TECO.TEC, then TECO.TEC must be placed on SYS:. H.17 ARITHMETIC PRECISION TECO-8 performs 13-bit arithmetic except that multiplication and division by negative numbers gives unpredictable results. All numbers stored in Q-registers are 13 bits long. Number stored in flags (such as ET, EU, etc.) are only 12-bits long. When storing a number into a flag, the high order (sign bit) is lost. When using the value of a flag in an arithmetic expression, the 12-bit value is sign extended first. H.18 ALTERNATE STARTING ADDRESS The normal starting address of TECO is location 00200. In this (normal) mode, TECO will simulate tabs by spaces on type out and will simulate vertical tabs and form feeds by line feeds. If your terminal has hardware tabs and vertical tabs (such as a KSR-35), then TECO can take advantage of these features. To enable this ability, you should change TECO's starting address to be 05200. This can be done by the monitor commands: .GET SYS:TECO .SAVE SYS:TECO;5200 H.19 VT05 SUPPORT Standard TECO Page H-12 Appendix H TECO will automatically handle command string scope editing correctly on a VT05. The VT support (obtained via use of the -1W command) will handle VT05's correctly. The VTEDIT macro does not currently support the VT05 keypad. Standard TECO Page I-1 Appendix I APPENDIX I TOPS-10 OPERATING CHARACTERISTICS TMPCOR SUPPORT The EQ and E% commands support the pseudo-device TMP: for TMPCOR. Only the first three letters of the file name will be used, to try and access a TMPCOR file. If that fails, it will try nnnNAM.TMP where nnn is your job number and NAM is the three-character name. For example: for job 23, EQqTMP:FOOBAR$ will read TMPCOR file FOO or 023FOO.TMP. Q-REGISTER NAMES Any printable character (except open parenthesis) is valid as a Q-register name. A Q-register whose name is a lower case alphabetic character is the same as the Q-register whose name consists of the corresponding upper case letter. Thus Qa and QA are equivalent commands. Q-register names may also be up to 6 characters long, by enclosing the name in parentheses. For example, Q(FOOBAR). Q-register names may contain any printable characters, however all characters other than letters, digits, dollar-sign, space, and underline are reserved for special use by TECO. A Q-register name consisting entirely of zero or more spaces is the same as Q-register (), which is special and discussed below. Trailing spaces in Q-register names are discarded, and lower case is converted to upper case. REFERENCING THE TEXT BUFFER AS A Q-REGISTER The Q-register with the null name: () is the text buffer. The numeric part of this Q-register is the value of dot. The sequence [A ]() causes Q-register A to share with the text buffer. The old main text buffer is lost (unless it is also sharing with some Q-register or if it has been saved on the Q-register push-down list). The text in Q-register A becomes the text buffer and the numeric part of Q-register A is used for "." if it is in range, otherwise dot is set to 0. SHARING OF Q-REGISTER POINTERS Q-registers may share their text with each other and with the text buffer as a result of [ and ] commands. When a Q-register is pushed ontot he Q-register pushdown list, all that is pushed is the numeric part of the Q-register and a pointer to the text part of the Q-register. Thus a command such as [A ]B would cause Q-registers A and B to share the same text. The commands X, ^U, and EQ could be applied to either Q-register without modifying the other, since the Q-register is unbound from its previous text first. However, the colon-modified forms of X and ^U append to the existing text, so a :X or :^U command for either of them would affect the other. Standard TECO Page I-2 Appendix I Standard TECO Page J-1 Appendix J APPENDIX J TECO.TEC & TECO.INI TECO.TEC - the TECO command responder Upon start up, TECO.TEC looks for a file named TECO.INI in your directory. If such a file is found, it is assumed to be a TECO macro and is executed before any command decoding. This feature can be inhibited by the /NOINI switch. TECO.TEC maintains a "memory" file with a name of "TECFnn.TMP" in your directory (the nn is your job number, 00 for RSX-11 systems). Every time you explicitly name a file to be edited, TECO places that file's name in the memory file. If you simply say TECO without any file specification, the memory file is read and the last edited file is re-edited. This feature can be inhibited by the /NOMEMORY switch. The following switches are recognized by TECO.TEC /NOINI Don't try to find or use the private initialization file TECO.INI. /NOMEMORY Don't read, write, or use the memory file TECFnn.TMP. /NOCREATE Don't automatically create a new file if the file specified by a TECO command doesn't already exist. /FIND Find the position marker in the file, delete the marker, then start editing. More information on the position marker is available in the VTEDIT documentation (VTEDIT.DOC). /INSPECT Only read the named file; don't edit it. /VTEDIT Automatically invoke the VTEDIT editing macro. /VTEDIT:SEEALL Invoke VTEDIT in SEEALL mode (see VTEDIT documentation). /VTEDIT:HOLD Invoke VTEDIT in hold screen mode (see VTEDIT documentation). /VTEDIT:SEEALL:HOLD Invoke VTEDIT in SEEALL and hold screen modes (see VTEDIT documentation). /SCROLL Automatically enter split screen scrolling mode with 1/4 of the screen's lines scrolled (see 7:W command). /SCROLL:n Automatically enter split screen scrolling mode with n lines scrolled (see 7:W command). Standard TECO Page J-2 Appendix J All of the above can be abbreviated to two (2) characters except /NOINI, /NOMEMORY, and /NOCREATE which must be at least three (3) characters. All of the switches apply to TECO commands, MAKE commands only recognize the /NOI, /NOM, /NOC, /VT, and /SC switches, and MUNG commands only take /NOI, /NOM, and /NOC. (/NOC is meaningless to MAKE and MUNG commands, but the switch is stripped off; /NOM is meaningless to MUNG, but the switch is also stripped off.) The following command formats are recognized by TECO.TEC TECO Re-edit last edited file (getting file name from memory file); effective EBfile$Y$$. TECO file Edit file "file"; effective EBfile$Y$$. TECO file2=file1 Create file "file2" from file "file1"; effective ERfile1$EWfile2$Y$$. TECO @file Use file "file" as an indirect command string; effective EIfile$$. (Not available under RSTS/E). MAKE file Create file "file"; effective EWfile$Y$$. MUNG file Use file "file" as an indirect command string; effective EIfile$$. MUNG file,text Use file "file" as an indirect command string passing the argument "text"; effective Itext$EIfile$$. For RSTS/E, TECO.TEC should be installed with a protection code of <104>. TECO.INI - the TECO initializer If you have a file by the name TECO.INI in your directory, TECO.TEC will automatically invoke it on every TECO start up. The file TECO.INI on the distribution medium is a model that you can build your own private TECO.INI from. Standard TECO Page K-1 Appendix K APPENDIX K CONFIGURING RSTS/E TECO-11 RSTS/E TECO-11 V35 can be re-configured to: 1. Include or exclude ":EG" support. 2. Include or exclude scope Rubout and Control/U support. 3. Include or exclude the "W" (scope watch) command. 4. Include or exclude the scrolling ("7:W") support. If :EG support is not included, all :EG commands will return a value of zero (for failure). The usefulness of :EG is questionable, but including :EG support adds less than 1K words to the TECO Run-Time System. Unfortunately, including :EG and/or scrolling support along with scope Rubout and Control/U support and the "W" command causes the TECO Run-Time System to be over 8k words... Scope support can be configured four ways: 1. No support at all for scope terminals. At a modest saving in size over #2 below, TECO can be configured without any support at all for scope type terminals. 2. Support for only Rubout and Control/U on scope terminals. TECO normally processes Rubouts by re-echoing the deleted character and processes Control/U by simply echoing ^U. If TECO is configured this way, Rubouts and Control/Us will actually erase the deleted character(s) from the screen. The size cost for this configuration is very modest. 3. Support for Rubout, Control/U, and the W (watch) command. This configuration includes the code that implements the W (scope watch) command. While the size cost is fairly large (about 1K words both in the TECO Run-Time System and in the user's job image), the W command allows TECO to serve as a keypad editor. 4. All of the above plus scrolling support. This configuration implements the special split-screen scrolling support. Scrolling can only operate on terminals with hardware scrolling region control (e.g., the VT100). Standard TECO Page K-2 Appendix K The pre-built TECO Run-Time System on the distribution kit (TECO.RTS) is configuration #3 above without :EG. You will need the following files from the distribution kit: 1. TECOLB.OBJ - Pre-assembled TECO and I/O package. 2. GEXIT.OBJ - Pre-assembled :EG command processor. 3. SCREEN.OBJ - Pre-assembled W command processor. 4. SCRINS.OBJ - Pre-assembled Insert Optimizer. 5. SCROLL.OBJ - Pre-assembled scrolling processor. 6. CRTRUB.OBJ - Pre-assembled scope type determination and sequences. You also will need the following from the RSTS/E distribution kit: 1. $PIP.SAV - To move files around. 2. $LINK.SAV - To link your new TECO. 3. ERR.STB - Error message globals for the TECO link. 4. $SILUS.SAV - To build your new TECO Run-Time System. 5. $UTILTY - To ADD your new TECO Run-Time System. Link TECO one of the following ways: Configuration #1, no :EG, no scope support RUN $LINK.SAV *TECO/Z,TECO,TECO=TECOLB/X/H:#177776/U:#4000/C *ERR.STB Round section? PATCH *^Z Configuration #2, :EG, no scope support RUN $LINK.SAV *TECO/Z,TECO,TECO=TECOLB/X/H:#177776/U:#4000/C *GEXIT/C *ERR.STB Round section? PATCH *^Z Standard TECO Page K-3 Appendix K Configuration #3, no :EG, Rubout & Control/U scope support RUN $LINK.SAV *TECO/Z,TECO,TECO=TECOLB/X/H:#177776/U:#4000/C *CRTRUB/C *ERR.STB Round section? PATCH *^Z Configuration #4, :EG, Rubout & Control/U scope support RUN $LINK.SAV *TECO/Z,TECO,TECO=TECOLB/X/H:#177776/U:#4000/C *GEXIT/C *CRTRUB/C *ERR.STB Round section? PATCH *^Z Configuration #5, no :EG, Rubout, Control/U, & Watch scope support RUN $LINK.SAV *TECO/Z,TECO,TECO=TECOLB/X/H:#177776/U:#4000/C *SCREEN/C *CRTRUB/C *ERR.STB Round section? PATCH *^Z Configuration #6, :EG, Rubout, Control/U, & Watch scope support RUN $LINK.SAV *TECO/Z,TECO,TECO=TECOLB/X/H:#177776/U:#4000/C *GEXIT/C *SCREEN/C *CRTRUB/C *ERR.STB Round section? PATCH *^Z Configurations #3 and #4 above require that the CRTRUB module be reassembled with the assembly conditionals "WATCH" and "SCROLL" defined as zero (see next section). To add the insert optimization module to configurations #5 and #6 above, you must change the line "*SCREEN/C" to "*SCREEN,SCRINS/C". Standard TECO Page K-4 Appendix K To add scrolling support to configurations #5 and #6 above, you must change the line "*SCREEN/C" to "*SCREEN,SCROLL/C" (or "*SCREEN,SCRINS,SCROLL/C"), and the CRTRUB module must be reassembled with the assembly conditionals "WATCH" and "SCROLL" defined as one (see next section). After linking TECO, you build your new TECO Run-Time System as follows: RUN $SILUS.SAV *TECO.RTS=TECO *^Z Now you can move TECO.RTS to account [0,1] being sure you make it contiguous: RUN $PIP.SAV *[0,1]*.*<60>/MODE:16.=TECO.RTS *^Z Now use UTILTY to REMOVE to old TECO and, then, ADD your new TECO: RUN $UTILTY ? REMOVE TECO ? ADD TECO ? ^Z Obviously, you can use some name other than TECO in the above PIP run to avoid clobbering a known good TECO.RTS while you are debugging. You can enter your trial TECO by saying D$=SYS(CHR$(9)+MID(SYS(CHR$(6)+CHR$(-10)+"xx"),7,4)+CHR$(0)) to BASIC-PLUS. Standard TECO Page L-1 Appendix L APPENDIX L CONFIGURING TECO-11 FOR FOREIGN SCOPE TERMINALS TECO-11 V35 can be re-configured to include support for foreign scope terminals. This section of these Release Notes is only intended for persons with MACRO programming knowledge; elsewise you can stop reading. TECO will support up to four (4) different scope type terminals in any given configuration. Each scope type is given a code. Scope type #1 is code 0, scope type #2 is code 2, scope type #3 is code 4, and scope type #4 is code 6. The pre-built TECO has support for: 1. VT52's, code 0 2. VT100's in VT52 mode, code 2 3. VT100's in ANSI mode, code 4 4. VT05's at 2400 baud (i.e., fill required), code 6 The algorithm for determining which of the above to use uses the terminal's current characteristic set (as set by TTYSET, SET TERMINAL, etc.). The pre-built algorithm is: 1. If not a scope then no scope support else; 2. If width is 72 then scope is a "VT05 with fill" else; 3. If width is not 80 then a default of VT52 scope support else; 4. If the "XON" characteristic (RSTS/E) is set or "SET TER/VT100" (VAX/VMS) then scope is a "VT100" else; 5. Scope is a "VT52". In order for a scope type terminal to qualify for Rubout and Control/U support it must: 1. Be able to erase a single character with a standard sequence The sequence , , must erase a single character and leave the cursor in the original position. 2. Be able to move the cursor up within column one line For example, , A on VT52's. Standard TECO Page L-2 Appendix L 3. Be able to erase a whole line and leave cursor at left margin For example, , , K on VT52's. In order for a scope type terminal to qualify for W (scope watch) command support it must: 1. Be able to position the cursor to "home" (upper left) For example, , H on VT52's. 2. Be able to do direct cursor addressing For example, , Y, , on VT52's. 3. Be able to erase to end of line without moving cursor For example, , K on VT52's. 4. Be able to scroll the screen up with cursor at screen's lower left For example, on VT52's. The following features are not required for W (scope watch) command support, but will be used if present: 1. Ability to scroll the screen down with cursor at screen's upper left For example, , I on VT52's. While this is an optional feature, the utility of the W command is very low without it. Any movement of the cursor up the page will cause a full screen re-draw. 2. Ability to erase to end of screen without moving cursor For example, , J on VT52's. This simply saves doing multiple erase to end of line's when the rest of the screen is to be blanked. On the other hand, any terminal with a changeable scrolling region (e.g., the VT100) should declare that it doesn't have this even if it does. The W command will do the multiple erase to end of line's and, thus, avoid clobbering anything out of the scrolling region. Standard TECO Page L-3 Appendix L 3. Ability to enter/exit reverse video For example, , [, 7, m on VT100's. All characters between the current "marked" position and the current cursor position will be displayed in reverse video. Some attribute other than reverse video can be used (e.g., blinking, bold, etc.). 4. Ability to enter/exit a "graphics" character set For example, , F on VT52's. Various points are marked with special graphics characters: 1. End-of-buffer without Form feed The "paragraph" symbol is used by VT52's. 2. End-of-buffer with Form feed The "solid rectangle" is used by VT52's. 3. A line which exceeds the right margin The "right arrow" is used by VT52's. 4. Cursor positioned between a Carriage return and Line feed The "down arrow" is used by VT52's. In the special "see all" mode, the following are also used: 1. Null spacing ("elipsis" on VT52's) 2. Horizontal tab ("degrees" on VT52's) 3. Line feed - same as #4 above 4. Vertical tab ("divided by" on VT52's) 5. Form feed - same as #2 above 6. Carriage return ("c/d" on VT52's) 7. Overprint carriage return ("5/" on VT52's) 8. Escape ("3/" on VT52's) 9. Control character prefix ("plus or minus" on VT52's) Standard TECO Page L-4 Appendix L The major qualification for scrolling support is the hardware capability of setting scrolling regions on the terminal. Reading the CRTRUB source should show you what is needed. You will need the following file from your distribution kit: 1. CRTRUB.MAC - Source for determining scope type and sequences. The first thing to do is to list CRTRUB.MAC, read it, and try to understand it. You will note that there is an assembly conditional called "WATCH". If it is left undefined, the CRTRUB assembly will include both scope rubout support and scope watch support. If it is defined to be zero then only scope rubout support will be generated. The "SCROLL" assembly conditional determines whether scrolling support is to be included. The correct operating system parameter should be defined to one (RSTS/E, RSX, or RT-11). If your CPU has the hardware SOB instruction, define I$$SOB to be one. If your CPU has the hardware divide (DIV) instruction, define I$$DIV to be one. (Note that VAX/VMS TECO is configured as RSX since it runs in compatibility mode; VAX always has hardware SOB and divide.) The rest of this exercise is left to the student... Now edit CRTRUB.MAC to be whatever you want. Assemble CRTRUB with the MACRO assembler; it needs neither any prefix file(s) nor uses any macro library. After you have CRTRUB assembled to your satisfaction, follow the directions for building TECO described earlier. Good luck! Standard TECO Page M-1 Appendix M APPENDIX M STORAGE AREAS Each storage area of TECO will be described below: TEXT BUFFER Name: H Value: Character string Purpose: To hold the text being edited by TECO. Initial value: null string Set by: Input (A, Y, etc.), Insert (I), Replace (FS, FR, etc.), and other commands. Used by: Output (P, PW, etc.), Search (S, N, etc.), Replace (FS, FN, etc.), and other commands. Typed by: HT --------------------------------------------------------- TEXT BUFFER POINTER REGISTER Name: . Value: Non-negative integer Purpose: To hold a non-negative integer that is the number of the pointer position that the text buffer pointer is currently positioned at. Initial value: 0 Set by: Pointer positioning commands (J, C, R, etc.), Search commands (S, etc.), and other commands. Used by: All position relative commands and, under its name ".", whenever used within an arithmetic expression. Typed by: .= --------------------------------------------------------- Standard TECO PAGE M-2 Storage Areas TEXT BUFFER SIZE REGISTER Name: Z Value: Non-negative integer Purpose: To hold a non-negative integer that is the number of characters in the entire text buffer. Initial value: 0 Set by: Any command that inserts (I, etc.) or deletes (D, K, etc.) from the text buffer. Used by: Using its name, "Z", in any arithmetic expression. Typed by: Z= --------------------------------------------------------- NUMERIC Q-REGISTERS Names: A,B,C,...,Z,0,1,2,...,9 Note: Additional Q-registers are allowed in TECO-10; consult appendix E. Value: The numeric portion of each Q-register contains one integer. Purpose: To hold an integer, for example, a pointer position. Initial value: 0 Set by: The U command. Used by: The Q and % commands. Typed by: Qq= --------------------------------------------------------- Standard TECO PAGE M-3 Storage Areas ALPHANUMERIC Q-REGISTERS Names: A,B,C,...,Z,0,1,2,...,9 Note: TECO-10 has additional Q-registers. See appendix E. Value: The text storage area of each Q-register can contain one string (including the null string). Purpose: To hold a portion of text or to hold a TECO command string for execution as a subroutine (macro). Set by: X and ^U TECO commands, and * immediate action command. Used by: G and M command. Initial value: null string Typed by: :Gq Executed by: Mq Note: Each Q-register contains both a numeric portion and a text portion. These are independent areas within the Q-register. --------------------------------------------------------- Q-REGISTER PUSHDOWN LIST Values: This is a stack of pairs of values, one numeric value and one character string. Purpose: To save for later restoration the values of a Q-register, or to pass arguments to a TECO subroutine. Initial value: empty Set by: The [ command. Used by: The ] command. Note: The stack is not cleared when TECO returns to prompt level. --------------------------------------------------------- Standard TECO PAGE M-4 Storage Areas SEARCH STRING BUFFER Name: _ [TECO-11 only] Value: character string Purpose: To accumulate and hold the string that a TECO command is searching for. Initial value: null string Set by: Any search command (S, N, _, FS, etc.). Used by: Any search command that specifies a null search string. Also used by TECO-11 via the commands G_ and Q_. Typed by: :G_ [TECO-11 only] --------------------------------------------------------- FILESPEC BUFFER Name: * [TECO-11 only] Value: character string Purpose: To accumulate and hold the file specification used by a TECO command. Set by: Any TECO command that specifies a file specification (ER, EW, EB, etc.). Used by: The G* and Q* commands. [TECO-11 only] Typed by: :G* [TECO-11 only] --------------------------------------------------------- Standard TECO PAGE M-5 Storage Areas FORM FEED FLAG Name: ^E Value: 0 (false) or -1 (true) Purpose: To indicate to the user whether the last data append stopped because a form feed was encountered in the input file or because the text buffer was nearly full. Initial value: 0 Set by: The Y and A commands. Used by: The P and N commands and any reference to the ^E flag by name in an arithmetic expression. Typed by: ^E= --------------------------------------------------------- END OF FILE FLAG Name: ^N Value: 0 (false) or -1 (true) Purpose: To indicate whether or not end-of-file on the input file has been encountered. Initial value: 0 Set by: Set to -1 by a command that reads input (Y, A, N, P, etc.) if there is no more input to be read. Set to 0 by a command that opens a new input file (ER or EB). Used by: Any command that references the ^N flag by name in an arithmetic expression. Typed by: ^N= --------------------------------------------------------- Standard TECO PAGE M-6 Storage Areas SEARCH MODE FLAG Name: ^X Value: 0 (either case mode) or -1 (exact case mode) Purpose: Specifies whether alphabetic characters in search strings must match exactly (-1) or whether either case of the same character is considered a match (0). Initial value: 0 Set by: n^X Used by: Search matching algorithm and any use of the flag by name (with no argument) in an arithmetic expression. Typed by: ^X= --------------------------------------------------------- EDIT LEVEL FLAG Name: ED Purpose: A bit-encoded integer. Each bit controls various TECO editing features. Initial value: Operating system dependent. See appendices. Set by: nED Used by: Any reference to this flag by name (with no argument) in an arithmetic expression. The search string builder, the text reading commands, and search failure handling all use bits in the ED flag (see section 5.14). Typed by: ED= --------------------------------------------------------- Standard TECO PAGE M-7 Storage Areas HELP LEVEL FLAG Name: EH Value: A bit-encoded integer Purpose: Each bit (or group of bits) determines properties about how TECO should handle error conditions. Initial value: 0 Set by: nEH Used by: TECO error message processor and any command that references this flag by name (with no arguments) in an arithmetic expression. Typed by: EH= --------------------------------------------------------- VERSION NUMBER FLAG Name: EO Value: An integer Purpose: Specifies what version of TECO is running. This version number is known as the EO level and may or may not be changed on each release. Set by: nEO command reserved for possible future use. Used by: Any reference to flag by name in an arithmetic expression. TECO macros may wish to interrogate this flag if they wish to use features of TECO that are not standardized across all implementations. Typed by: EO= --------------------------------------------------------- Standard TECO PAGE M-8 Storage Areas SEARCH VERIFICATION FLAG Name: ES Value: An integer Purpose: Specifies whether or not special action should be taken after a successful top-level search. Initial value: 0 Set by: nES Used by: TECO search processor and any reference to this flag by name (with no argument) in an arithmetic expression. Typed by: ES= --------------------------------------------------------- TERMINAL MODE FLAG Name: ET Value: A bit-encoded integer Purpose: Each bit controls the way TECO handles various terminal-related characteristics. Initial value: Operating system dependent. See appendices. Set by: nET and TECO initially sets various bits to indicate the presence of specific terminal properties. (See appendices.) Used by: TECO terminal service and any reference to this flag by name (with no arguments) in an arithmetic expression. Typed by: ET= --------------------------------------------------------- Standard TECO PAGE M-9 Storage Areas UPPER/LOWER CASE FLAG Name: EU Value: An integer Purpose: To indicate the manner in which alphabetic characters should be flagged when typed on a terminal. Initial value: -1 if the editing terminal supports lower case typeout; 0 if not. Set by: nEU Used by: TECO terminal service and any reference to this flag by name (with no arguments) in an arithmetic expression. Typed by: EU= --------------------------------------------------------- EDIT VERIFY FLAG [TECO-11 only] Name: EV Purpose: To control the action of TECO after the execution of a command string. Value: An integer Initial value: 0 Set by: nEV Used by: TECO command executer and any reference to this flag by name (with no arguments) in an arithmetic expression. Typed by: EV= --------------------------------------------------------- Standard TECO PAGE M-10 Storage Areas COMMAND STRING BUFFER Value: character string Purpose: To accumulate the command string as TECO accepts it, character by character, from the type-in buffer, and hold it until it is ready to be executed. Initial value: Operating system dependent (see appendices) Set by: Type-in from the user terminal (or indirect file). Used by: The TECO command interpreter. Typed by: The * immediate action command. Executed by: The $$ immediate action command. --------------------------------------------------------- COMMAND STRING PUSHDOWN STACK Values: This is a stack of character strings. Purpose: To save the current command string when it calls a subroutine (via the M command). Set by: TECO, when an M command is begun. Used by: TECO, when an M command is completed. Note: This stack is reset every time TECO returns to its * prompt. --------------------------------------------------------- Standard TECO PAGE M-11 Storage Areas COMMAND REGISTER BACKUP REGISTER Value: character string Purpose: To retain the most recent command string. Set by: TECO from the command register. Used by: The *q immediate action command (to retrieve the last command string.) Note: In TECO-8, this register is retrieved into Q-register Z via use of the * immediate action command. --------------------------------------------------------- TYPE-AHEAD BUFFER Value: Character string Purpose: To hold incoming characters from the user terminal until TECO is free to echo them and interpret them. Set by: Type-in from the user terminal. Used by: TECO. Note: This register is mentioned because its presence allows the TECO user to continue typing even when TECO is too busy to accept type-in. This register is maintained by the operating system in many implementations. In TECO-8, this register is available only if VT support is present. --------------------------------------------------------- Standard TECO PAGE M-12 Storage Areas INPUT/OUTPUT BUFFERS Value: Character string Purpose: To hold characters transmitted between TECO and operating system files until they can be accepted at their destination. Note: These buffers are mentioned because a too-sudden exit from TECO can cause the loss of the contents of these buffers. In most operating systems, these buffers are maintained by operating system services, rather than by TECO itself. Standard TECO Page N-1 Glossary APPENDIX M GLOSSARY OF OBSCURE TECO TERMS Abort-on-error bit The 128's bit of the ET flag. If this bit is set, then TECO will abort execution on encountering an error (after printing the error message) and control returns to the operating system. This bit is initially set when TECO starts up, but is reset whenever TECO issues its prompt. One of several characters that TECO treats specially for use as a delimiter. Known as ESCAPE in more recent times, but traditional TECO users will still go on ending their command strings with "ALT" "ALT". Usually shown as $ in this manual. Anchored search A search (S) or search and replace (FS) command that is preceded by a ::. This indicates that the search must match the characters immediately following the current pointer position. If these characters do not match, no further searching is performed and the text buffer pointer does not move. Argument pair A command of the form m,n where m and n are numbers (or TECO commands that return numbers). When used before a command that normally acts on lines, the argument pair causes the command to work on characters. The characters specified by this argument pair is the set of characters between pointer positions m and n. The number m should normally be less than or equal to n. ASCII code The American Standard Code for Information Interchange. A code used by TECO to represent characters internally. Consult Appendix A for details. @-sign modified command A command that is preceded by an @-sign modifier. @-sign modifier An at-sign (@) that proceeds a command. It indicates to TECO that the string argument to the command is to delimited on both sides by a user-supplied delimiter rather than to be delimited only at the end by a TECO-designated delimiter (normally ). be automatically typed out. The ES flag may be Standard TECO Page N-2 Glossary Automatic type out The feature of TECO that causes lines of text to used to control the automatic type out of lines after search commands, and the EV flag may be used to cause automatic type out of lines after command execution. Auto-Trace Mode A mode that TECO goes into when the 4's bit of the EH (Help-level) flag is set. In this mode, TECO will automatically print out the erroneous command string after an error occurs. Backup Protection The process of preserving the user's original file (as a backup) when editing that file with the EB (Edit with Backup) command. Backwards searches A search that proceeds in the backwards direction. If the string being looked for does not occur at the current pointer position, the pointer position is moved back one character and the search is tried again. This continues until the string is found or until the boundary of the search has been reached or until the beginning of the current text buffer has been reached. Backward searches are initiated by using a negative argument to a search command or by using an argument pair m,n with m greater than n to an FB or FC command. Bounded searches A search command that requires searching only a portion of the text buffer. Of particular importance is the case where you only want to search the current line for a given string. Bounded searches are accomplished using the FB command. Case flagging A mode of TECO wherein, on type out, it will flag alphabetic characters (in either upper or lower case) by preceding them with a single quote. Lower case flagging is particularly useful on terminals that do not display lower case. Case falgging is controlled by EU, the cae flag. Setting EU to 0 sets lower case flagging mode; setting EU to 1 sets upper case flagging mode, and setting EU to -1 removes all case flagging. Character-oriented editor An editor that allows modification of single characters, so that if just one character of a line is wrong, the entire line does not have to be retyped. TECO is a character-oriented editor. Standard TECO Page N-3 Glossary Colon-modified Command A command that is preceded by a colon (:) modifier. Colon-modifier A colon preceding a TECO command, used to indicate that the action of the command is to change. Frequently indicates that the command is to return a value (-1 if the command succeeded, 0 if the command failed). Command line The current line of the command string that is being typed into TECO. Command string scope editing The feature of TECO that is enabled when editing is performed on a CRT terminal. In this mode, typing the immediate action command causes the character deleted from the command string to physically disappear from the screen. Other commands, such as also behave differently, taking best advantage of the properties of a video terminal. Command string The string of TECO commands that is currently being typed into TECO, or is currently being executed by TECO. Comment An informative message used within a TECO program, to make the code more readable. The comment explains the meaning and purpose of the associated TECO commands. The comment is enclosed in exclamation marks. Compile-class command A set of operating systems commands (such as COMPILE) that causes compilation (translation) of a source file written in a computer language into machine instructions. The EG$ command is useful to finish an editing session and re-execute the last compile-class command (normally a command that compiles the file that was just edited). Conditional A TECO language construct used to specify code to be conditionally executed depending upon the results of some test. The most general form of the TECO conditional is n"X | ' which tests the number n using condition X (See section 5.13 for details). The commands specified by the are executed if the condition Standard TECO Page N-4 Glossary succeeds, otherwise the commands specified by the are executed. Control-character An ASCII character whose octal code is in the range 0-37. Usually denoted in this manual by where X is the character whose ASCII code is 100 (octal) greater thant he ASCII code for the control character being represented. TECO displays such a character as ^X (Caret-X) except for , , , , AND which have their normal display, and which is displayed as $ (dollar sign). Anytime a single control-character, is a valid TECO command, the two-character sequence, ^X, may be used instead. trapping A mode of operation wherein TECO will regain control (rather than the operating system) when or is typed on the user's terminal to abort execution of the current command string. trapping is enabled by setting the high-order bit of the ET flag. Current character The character immediately following the current text buffer pointer position. Cursor A visible pattern on a CRT terminal (usually blinking) that would specify to a true scope editor (like VTEDIT) the current location of the text buffer pointer, or which would specify the location where subsequently typed characters would be displayed. Destructive search A form of global search in which pages of text that are passed over (because they did not contain the string being searched for) are discarded rather than written to the output file. Destructive searches are initiated in TECO via use of the _ command. Display editor A true display editor is on which makes efficent use of a CRT terminal or display scope. Such an editor maintains a "window" into the text being edited. As characters are typed on the terminal, these characters immediately are entered into the text buffer and the window is immediately updated to reflect this change. With the help of some macro support, TECO can be made to be a true display editor. Standard TECO Page N-5 Glossary Dot A mnemonic for "the current text buffer pointer position". Stems from the fact that the . (dot, or period) TECO command returns this number as its value. E Command One of several two-character TECO commands that start with the letter 'E'. Echo mode A normal mode of operation in which TECO will automatically echo (display) each character that is typed in response to a ^T command. Opposite of no-echo mode. This mode is controlled by the 8's bit of the ET flag. (0 means no-echo mode.) ED flag The edit level flag. Edit-class command A type of operating system command (such as MAKE and TECO) that specifies that file editing is to occur. Many operating systems remember the argument specified with the last Edit-class command, so that the next time an edit-class command is used without an argument, the previous argument can be recalled. Edit level flag A bit-encoded flag, referenced by the ED command, that describes how TECO should behave with reference to certain features. See section 5.16 for more details. Edit verify flag A flag that describes how TECO should act after processing of a command string. This flag can be set so that TECO will display the line just edited on the terminal after each command. See section 5.16 for more details. EH flag The help level flag. Either-case search mode A standard mode of operation in which alphabetic characters specified within a search string are permitted to match a corresponding character of either upper or lower case. Else-clause The part of a conditional command that is executed if the condition is not satisfied. In TECO, these are the commands that occur between the | and the ' characters within the conditional construct. End-of-file flag A read-only flag, referenced by the ^N command Standard TECO Page N-6 Glossary that specifies whether or not end-of-file has been seen on the currently selected input stream. A value of 0 means that end-of-file has not been seen; a value of -1 means that end-of-file has beenr eached. This falg is initially 0 and is reset to 0 each time a new file is selected for input. EO level The current version level of TECO-10. ES flag The search verification flag. The character whose ASCII code is 33 (octal). It is a general-purpose delimiter used by TECO. Traditionally known as an . ET flag The terminal characteristics flag EU flag The upper/lower case flag. EV flag The edit verify flag. Exact-case search mode A mode of operation in which alphabetic characters within a search string must match the exact case (upper case or lower case) of character specified. Exit Protection A protective feature of TECO that prevents a user from exiting TECO if a potential los of data is imminent. The EX and EG commands are aborted (with the ?NFO error message) if there is text in the text buffer, but no output file is open. F Command One of several two-character TECO commands that start with the letter 'F'. Flag A data register used by TECO to control various modes of operation. The contets of the flag are set by specifying the new value before the flag name; and the contents are returned by using the flag name without a numeric argument. The TECO flags are: ^X, ^E, ^N, ED, EH, EO, ES, ET, EU, and EV. Flow command A TECO-11 command that is used to flow (branch) to a particular flow control character. The current flow commands are F<, F>, F', and F|. Form feed flag A read-only flag, referenced by the ^E command that specifies whether the previous append from the input file terminated because of encountering Standard TECO Page N-7 Glossary a form feed character in the input file, or because the text buffer became nearly full. The value of this flag is automatically set to -1 by TECO if input is terminated by the presence of a form feed character in the input file. Garbage collection A process used by TECO-10 to collect unused memory when more memory is required. Global search A type of search that continues through the entire input file until the specified characters are found. Successive pages of the file are read into the text buffer and then written out into the output file (if the strign is not located). Global searches in TECO are initiated via the N command. Hard-copy editing mode A mode of operation that TECO uses when the user's terminal is not a CRT. In this mode, when a character is rubbed out using the key, the rubbed-out character is re-typed on the terminal as a visible indication that this character was rubbed out. Opposite of scope editing mode. This mode can be entered, even on a scope terminal, by turning off the 2's bit of the ET flag. Help level flag A bit-encoded flag, referenced by the EH command, that controls properties of TECO having to do with error messages and user assistance. Immediate Action Command A special command to TECO that takes immediate effect, requiring no s to begin its execution. Such commands are usually used to perform editing of the TECO command string currently being entered into TECO. For example, the commands and are immediate action commands. Immediate aid A type of immediate action command that must be typed as the first keystroke after TECO's prompt and provides assistance to the user. Examples of such aids are: ?, /, *q, , and . Iteration A language construct that permits a sequence of commands to be re-executed indefinitely or a given number of times. In TECO, this is accomplished by enclosing the commands in angle brackets. Standard TECO Page N-8 Glossary Kernel The TECO-11 kernel refers to the TECO-11 module that implements all those features of TECO-11 that are common to all PDP-11 operating systems. Operating system specific features and the interface to the operating system is accomplished by linking an I/O module tailored for the desired operating system with the kernel. Keypad editor A true scope editor that uses special keys on the terminal (such as a VT52 or VT100) to control editing functions. VTEDIT is an example of a keypad editor. Line A portion of text delimited by , , , or the beginning or end of the text buffer. The final delimter is considered to be part of the line. Line-numbered file In TOPS-10, an ASCII file that contains line numnbers embedded in to the start of each line. TECO does not require these line numbers, but can handle them if they are present. They can also be generated or suppressed via the /GENLSN and /SUPLSN switches respectively. Line-oriented editor An editor that primarily uses line numbers to direct editing, and most of whose commands are line-oriented. TECO is a character-oriented editor but also has many commands that work on lines. Line-wrap mode A standard mode of TECO's window support wherein lines that are too long to fit on a single physical line of the user's terminal are automatically continued on the next line. Opposite of truncate mode. Literal Type out mode A mode that TECO can be put into by setting the 1's bit in the ET flag. In this mode, any characters typed by a TECO program via use of one of the commands T, V, ^A, or :G, will be displayed on the user's terminal without any modification. When not in this mode, TECO will convert characters that normally do not print to a form that can be displayed on the user's terminal (e.g. displays as ^X and displays as $). Literal type out mode is useful when trying to do real-time displays on a CRT terminal. Normal (up-arrow) mode is particularly useful to Standard TECO Page N-9 Glossary let you see what characters are really in your file. Log file An audit trail that TECO-10 can keep showing all the commands that were typed to TECO and/or all the type out made by TECO. This is useful for reviewing what went wrong with a 'bad' edit. The log file is initiated witht he EL command (see Appendix C). Macro A sequence of TECO commands intended to be loaded into a Q-register and executed as a TECO program. Macro level Two commands within the same TECO macro are said to be at the same macro level. Match control construct A command, consisting of certain special characters, used within a search string to indicate to TECO that special groups of characters are permitted to match at this point. Memory Expansion TECO's act of acquiring additional storage from the operating system when te currently allocated storage is insufficient to handle the current TECO command. Typically, TECO will attempt to acquire this additional memory before it completely runs out of memory, so as to allow a 'buffer zone' for the user. This allows him to complete a few more commands even in the case where TECO is unable to get more memory. The informative message "[nK Bytes]" or its equivalent is printed onthe terminal informing the user that memory usage has expanded. Mung A recursive acronym for "Mung Until No Good"; an act applied by novice TECO users to their source files. MUNG Command An operating system command used to invoke a pre-written TECO program. The most general form of this command is "MUNG file,data" where "file" is the name of a TECO source program, and "data" is data to be passed to that program. Nest level Two TECO commands are said to be at the same nest level if one is not outside of a conditional that contains the other. No-echo mode A mode of operation in which TECO will not automatically echo (display) the character typed Standard TECO Page N-10 Glossary by the user in response to the ^T command. This mode is entered by setting the 8's bit of the ET flag. Opposite of echo mode. Page A portion of text delimited by form feeds. The form feeds are not considered to be part of the page. Sometimes the term 'page' is used to refer to all the text currently in the text buffer. Panic Mode A condition that occurs (on small, single-user operating systems), when, in the middle of outputting during an edit, the output device fills up so that the I/O transfer cannot continue. TECO recovers gracefully from this condition by printing the ?FUL error message and returning control to TECO without any loss of data. At this point, the user closes the current output file and opens another one on another device (with more room) and resumes editing. At a subsequent time, the two parts of his file are concatenated back together. Pipeline editor An editor which only makes sequential edits to a file. The file to be edited is read into the text buffer one piece at a time. Each piece is edited and then written out. Once a piece has been written out, further editing to that piece is not possible unless the output file is re-opened in a later edit as a new file to be edited. TECO is a pipeline editor. Pointer preservation mode A mode of operation in which the text buffer pointer will not change after a failing search. This mode is controlled by the 16's bit of the ED flag. Primary input stream A term used by TECO-11 to refer to the main input file that TECO is using. Primary output stream A term used by TECO-11 to refer to the main output file that TECO is using. Prompt level A TECO command is said to be executed from prompt level if it was typed in directly in response to TECO's prompt, rather than being executed from a macro. Q-register One of 36 special-purpose registers used by TECO. Standard TECO Page N-11 Glossary Each register can hold both a number and a string of text. Of particular importance is the ability to store TECO command strings in Q-registers to be used as 'subroutines'. Q-register push down list A last-in first-out stack available to users for saving and restoring the contents of Q-registers. Read-with-no-wait mode A mode of operation in which the ^T command will not hang until a key is typed on the user's terminal. In this mode, if no key has been struck, TECO returns a -1 as the value of the ^T command. This mode is entered by setting the 32's bit of te ET flag. Search verification flag A flag, referenced by the ES command, that controls the action of TECO subsequent to the execution of a command string containg a search command. Proper setting of this flag will enable the user to verify that the search located the correct string, by having the line containing the string found displayed on the terminal. See section 5.16 for more details. Search mode flag A flag, referenced by the ^X command, that controls how TECO treats alphabetical characters within search strings. This flag is used to put TECO into either exact-case mode, or either-case mode. If the ^X flag is set to 0, then either case matches in searches. If the ^X flag is set to 1, then exact case matches are required. Secondary input stream A term used by TECO-11 to refer to an auxiliary input "channel" that was formed by use of the EP command. Secondary output stream A term used by TECO-11 to refer to an auxiliary output "channel" that was formed by use of the EA command. See appendix C for details. Scope editing mode A mode of TECO in which command line scope editing (q.v.) algorithms are used. This mode is enabled by setting the 2's bit of the ET flag. It is usually automatically enabled by TECO if the operating system can detect that the user has invoked TECO from a scope terminal. Opposite of hard-copy editing mode. Standard TECO Page N-12 Glossary Split Q-registers The feature of TECO that permits storing of both a number and a string within a Q-register. Each Q-register can be considered to consist of two compartments. String build construct A command, consisting of special characters, used within a text argument to build up the contents of the text argument from other components. SUPER TECO mode A mode of TECO-8 wherein TECO will read past the end-of-file mark (CTRL/Z) of a sequential ASCII file. This mode is enabled by using the /S switch on an ER, EW, or EB command and is terminated when an ER, EW, or EB command is issued with no /S switch. This mode is useful for scanning through mass storage devices in an attempt to recover data from files that had previously been deleted. Switch A construct of the form /SWITCH used within a command that takes a filespecification, to modify the action of the command or attributes of the file specified. Tag A label specified within exclamation marks to mark a point within a TECO program. Control can be transferred to this point by the use of a GOTO (Otag$) command. TECO Text Editor and COrrector program. TECO.INI A file containing TECO commands that is used as a user's private initialization file. When TECO starts up, it looks for such a file in the user's area, and if it finds one, the TECO commands in this file are executed before editing commences. TECO.TEC A TECO macro used by many operating systems to parse the user's edit-class commands. TECO I/O mode A mode of I/O operation under the RSX-11 operating system, in which the system buffers most characters and returns control to the caller (usually TECO) only when interesting characters (such as , , etc.) are typed. TECO's prompt refers to the asterisk (*) that TECO prints to indicate that it is ready to accept commands. TECO SIG A DECUS Special Interest Group, consisting of Standard TECO Page N-13 Glossary users who are dedicated to the spread of, improvement of, and standardization of TECO. Terminal characteristics flag A bit-encoded flag, referenced via the ET command, that contains information about the user's editing terminal and specifies in what modes TECO should support it. Text buffer The main buffer used by TECO to hold the text to be edited. Text buffer pointer A pointer that marks the position within the text buffer where TECO is currently 'at'. This pointer always points to positions between characters; it never points at a character. The current character is considred to be the character immediately to the right of the current position of the text buffer pointer. Then-clause The set of commands within a conditional that are executed if the condition is satisfied. In TECO, these commands immediately follow the "X at the start of the conditional. They are terminated by a | or ' character. Tracing The act of watching the command-by-command execution of a TECO program. This is accomplished by putting TECO into trace mode, via use of the ? command. Trace mode A mode of TECO wherein each command that is executed by TECO is also displayed on the user's terminal as it is being executed. This mode is useful for debugging complicated TECO programs. TECO is toggled in and out of this mode via use of the ? command. See section 5.18.4 for more details. Truncate mode A mode of TECO's window support wherein lines that are too long to fit on a single physical line of the user's terminal are truncated when the right margin of the scope is encountered. This mode is entered by setting the 256's bit in the ET flag. Opposite of line-wrap mode. Type-out-time command A special command that makes sense only while TECO is typing out text on the terminal. These commands are , , and and Standard TECO Page N-14 Glossary affect the type out. Consult the appropriate appendix to see what your operating system does if these commands are issued at a time when TECO is not typing out text. Up-arrow mode A standard mode of operation wherein upon type out, TECO will display control characters by typing the visible two-character sequence ^X to represent the control character . On many older terminals, the caret character (^), whose octal ASCII code is 136, prints as an up-arrow. Some control characters are excepted in up-arrow mode, notably , , , , and . Also, in this mode, the character is displayed as a dollar sign ($). Upper/lower case flag A flag, referenced by the EU command, that specifies whether or not case flagging is to occur. If set to -1, no case flagging occurs. If set to 0, lower case characters are flagged on type out. If set to +1, upper case characters are flagged on type out. View all mode A mode of window operation in which all characters have a distinctive visible display, including characters such as , , and , which normally do not display. War and Peace mode A mode of operation in which TECO outputs a large informative paragraph of information automatically upon encountering an error in a user's program. This paragraph of information describes the error in painstaking detail and tells the user how to recover. This mode is entered by setting the help level to 3. This mode is particularly useful to Novices and particularly obnoxious to experts. Window The portion of the text buffer that is currently being displayed on the user's terminal or auxiliary display device. Window support Assembly language code, built into TECO, that maintains a window into the text buffer on the user's terminal or auxiliary display device. Yank protection A feature of TECO wherein any Y, _, or F_ command that will potentially destroy valid data is aborted. This mode is normally enabled and will Standard TECO Page N-15 Glossary cause any of the aforementioned commands to abort with the ?YCA error message if there is text in the text buffer and an output file is open. This feature can be disabled by turning off the 2's bit in the ED flag. Standard TECO Page N-16 Glossary Standard TECO Index INDEX TO TECO COMMANDS AND SPECIAL CHARACTERS A Append one line to buffer 5-11,6-2 nA ASCII value of char in buffer 5-39,6-4 ^A Output message to terminal 5-16,6-5 B 0 (beginning of buffer) 5-39,6-7 ^B Current date 5-40,6-8 Type out previous line 4-4 C Advance n characters 5-13,6-9 ^C Stop execution 5-6,5-47,6-11 Ignored in commands D Delete n characters 5-18,6-12 ^D Set radix to decimal 5-36,6-14 ^E Form Feed flag 5-40,6-15 EA Select secondary output stream 5-7,6-16 EB Open input and output 5-3,6-17 EC Close out (copy in to out and close) 5-5,6-19 ED Edit mode flag 5-52,6-20 EF Close output file 5-5,6-22 EG Close out and exit with command 5-5,6-24 EH Help level flag 5-53,6-26 EI Open indirect command file 5-7,6-27 EJ Return Environment Characteristics 5-50,6-28 EK Kill output file 5-5,6-29 EL Open Log File 5-5,6-30 EN Wildcard lookup 5-9,6-31 EO Version of TECO 5-54,6-32 EP Select secondary input stream 5-7,6-33 EQ Read into Q-register 5-10,6-34 ER Open input file 5-3,5-7,6-35 ES Search verification flag 5-54,6-36 String and command terminator 4-2 ET Type out control flag 5-54,6-38 EU Case flagging flag 5-56,6-41 EV Edit verify flag 5-56,6-42 EW Open output file 5-3,5-7,6-43 EX close out and exit 5-6,6-44 EY Unprotected read into buffer 5-12,6-45 EZ Open & Initialize file 5-6,6-46 E% Write file from Q-register 5-10,6-47 E_ Destructive unprotected search 5-23,6-48 ^EA (Match char) Match alphabetics 5-29 ^EB (Match char) Match separator char 5-28 ^EC (Match char) Match Symbol Constituent 5-29 ^ED (Match char) Match numerics 5-29 ^EGq (Match char) Match contents of Q-reg 5-29 ^EL (Match char) Match line terminators 5-29 ^EM (Match char) Match several of next char 5-29 ^EQq (String char) Use contents of Q-reg q 5-28 ^ER (Match char) Match alphanumerics 5-29 ^ES (Match char) Match non-null space/tab 5-29 ^EUq (String char) Use char with val in Q-reg 5-28 Standard TECO Index ^EV (Match char) Match lower case alphabetic 5-29 ^EW (Match char) Match upper case alphabetic 5-29 ^EX (Match char) Match any character 5-29 ^Ennn (Match char) Match char ASCII code nnn 5-29 ^E[a,b..] (Match char) Match any of a,b,... 5-30 ^F Contents of console switch register 5-40,6-49 n^F Return terminal number 5-40, 6-50 FB Bounded Search 5-24,6-51 FC Bounded Search/Replace 5-25,6-52 FD Fast Search/Delete 5-18,5-25,6-53 Page terminator; Output Form Feed 1-3 FK Fast Search/Kill 5-19,5-25,6-54 FN Global string replace 5-25,6-55 FR Replace last string 5-18,5-21,6-57 FS Local string replace 5-25,6-58 F' Flow to end of conditional 5-46,6-60 F< Flow to start of iteration 5-46,6-61 F> Flow to end of iteration 5-46,6-62 F_ Global string replace, no output 5-25,6-63 F| Flow to else clause of conditional 5-46,6-64 Gq Get string from Q-reg q 5-33,6-65 ^G^G Kill command string 4-3 ^G Retype current command line 4-3 ^G* Retype current command input 4-3 H Equivalent to "B,Z" 5-39,6-66 ^H Current time of day 5-40,6-67 ^H See I Insert text 5-20,6-68 nI Insert ASCII character "n" 5-20,6-70 ^I See J Move pointer 5-13,6-72 ^J See K Kill n lines 5-18,6-73 ^K See L Advance n lines 5-14,6-75 ^L See Type out next line 4-4 Mq Execute string in Q-reg q 5-34,5-39,6-77 ^M See N Global search 5-23,6-79 ^N End of file flag 5-40,6-81 ^Nx (Match char) Match all but x 5-28 O Go to label 5-43,6-82 ^O Set radix to octal 5-36,6-84 ^O Kill terminal output 5-17 P Advance n pages 5-11,6-85 ^P Not a TECO command PW Write buffer n times 5-12,6-87 Qq Number in/size of Q-reg q 5-33,6-89 nQq Value of (n+1)th cha in Q-reg q 5-33,6-89 ^Qx (String char) Use x literally 5-27 R Back up n characters 5-14,6-90 ^R Test/reset current radix 5-36,6-91 ^Rx (String char) Use x literally 5-27 Standard TECO Index S Local search 5-22,6-92 ^S -(length) of last referenced string 5-40,6-94 ^S (Match char) Match separator char 5-28 T Type n lines 5-15,6-95 ^T ASCII value of next character typed 5-41,6-97 n^T Output ASCII character of value n 5-41,6-98 Insert tab and text 5-21,6-99 nUq Put number n into Q-reg q 5-31,6-100 ^U Kill command line 4-3 ^Uq Put string into Q-reg q 5-31,6-101 n^Uq Put ASCII char "n" into Q-reg q 5-31,6-101 V Type n current lines 5-15,6-102 ^V Lower-case conversion 5-66,6-103 ^Vx (String char) Force x to lower case 5-27 Not a TECO command W Scope "watch" 5-58,6-104 ^W Upper-case conversion 5-66,6-108 ^Wx (String char) Force x to upper case 5-27 Xq Put n lines into Q-reg q 5-32,6-109 ^X Search mode flag 5-57,6-111 ^X (Match char) Match any character 5-28 Y Read into buffer 5-12,6-112 ^Y Equivalent to ".+^S,." 5-41,6-114 Z End of buffer value 5-39,6-115 ^Z^Z^Z Terminate execution 4-3 ! Define label 5-43,6-116 " Start conditional 5-48,6-117 n"A Test for alphabetic 5-48,6-118 n"C Test for symbol constituent 5-48,6-118 n"D Test for numeric 5-49,6-118 n"E Test for equal to zero 5-49,6-118 n"F Test for false 5-49,6-118 n"G Test for greater than zero 5-49,6-118 n"L Test for less than zero 5-49,6-118 n"N Test for not equal to zero 5-49,6-118 n"R Test for alphanumeric 5-49,6-118 n"S Test for successful 5-49,6-118 n"T Test for true 5-49,6-118 n"U Test for unsuccessful 5-49,6-118 n"V Test for lower case 5-49,6-118 n"W Test for upper case 5-49,6-118 n"< Test for less than zero 5-49,6-118 n"E Test for equal to zero 5-49,6-118 n"> Test for greater than zero 5-49,6-118 # Logical OR 5-35 $ Not a TECO command n%q Add n to Q-reg q and return result 5-32,6-122 & Logical AND 5-35 ' End conditional 5-45,6-117 ( Expression grouping 5-35 ) Expression grouping 5-35 * Multiplication 5-35 *q Save last command 4-4 + Addition 5-35 Standard TECO Index , Argument separator 5-35 - Subtraction or negation 5-35 . Current pointer position 5-39,6-123 / More help on error 4-4 / Division 5-35 0-9 Digit : Colon modifier 6-124 ; Conditional exit from loop 5-44,6-126 n< Iterate n times 5-42,6-127 = Type in decimal, octal or hexadecimal 5-36,6-129 > End iteration 5-42,6-127 ? Toggle trace mode 4-4,6-132 @ Text delimiter modifier 6-131 [q Q-register push 5-34,6-132 ^[ See \ Value of digit string in buffer 5-37,5-39,6-133 n\ Convert n to digits in buffer 5-37,6-133 ^\ Not a TECO command ]q Q-register pop 5-32,6-134 ^] Not a TECO command ^^x ASCII value of x 5-41,6-135 _ Global search without output 5-23,6-136 ^_ Ones complement (logical NOT) 5-35 ` Not a TECO command a-z Treated the same as upper case A-Z { Not a TECO command | Else clause of conditional 5-45 } Not a TECO command ~ Not a TECO command Delete last character typed in 4-2