Digital Equipment Corporation TECO Text Editor and Corrector User Manual

INTRODUCTION TO
IECO
(TEXT EDITOR
AND CORRECTOR)
«>
INTRODUCTION TO TECO
(TEXT EDITOR AND CORRECTOR)
DEC-10-lJTECA-A-D
This document represents the software as of version 23 of TECO.
digital equipment corporation • maynard. massachusetts
First printing, May 1972
Second printing, Novemter 1974
Third printing, J~ne 1975
The information in this document is subject to change without notice
and should not be construed as a commitment by Digital Equipment
Corporation.
Digital Equipment Corporation assumes no responsibility
for any errors that may appear in this document.
The software described in this document is furnished under a license
and may be used or copied only in accordance with the terms of such
license.
Digital Equipment Corporation assumes no responsibility for the use
or reliability of its software on equipment that is not supplied by
DIGITAL.
Copyright
©
~972,
1973,
1974,
1975 by Digital Equipment Corporation
The postage prepaid READER'S COMMENTS form on the last page of this
document requests the user's critical evaluation to assist us in preparing future documentation.
The following are trademarks of Digital Equipment Corporation:
DIGITAL
DEC
PDP
DECUS
UNIBUS
COMPUTER LABS
COMTEX
DDT
DECCOMM
DECsystem-IO
DEC tape
DIBOL
EDUSYSTEM
FLIP CHIP
FOCAL
INDAC
LAB-8
DECsystem-20
MASSBUS
OMNIBUS
OS/8
PHA
RSTS
RSX
TYPESET-8
TYPESET-IO
TYPESET-II
CONTENTS
Page
CHAPTER 1
INTRODUCTION TO TECO
1.1
GENERAL OPERATING PROCEDURE
1-1
1 .2
INITlALIZA nON
1-2
1 .3
SPECIAL SYMBOLS USED IN THIS DOCUMENT
1-3
1 .4
GENERAL COMMAND STRING SYNTAX
1-4
1 .5
ERASING COMMANDS
1-5
1 .6
COMMAND ARGUMENTS
1-5
CHAPTER 2
TECO COMMANDS
2.1
INPUT COMMANDS
2-1
2.2
BUFFER POINT POSITIONING
2-2
2.3
TEXT TYPE-QIUT
2-4
2.4
DELETION COMMANDS
2-5
2.5
INSERTION COMMAND
2-6
2.6
OUTPUT COMMANDS
2-7
2.7
SPECIAL EXIT COMMANDS
2-8
2.8
SEARCH COMMANDS
2-9
CHAPTER 3
ERROR MESSAG ES
TABLES
1-1
3-1
Special Symbolls
TECO Error Messages
1-3
3-2
iii
CHAPTER 1
INTRODUCTION TO TECO
TEeo, a very powerful text editor, enables the advanced DECsystem-10 user to edit any ASC II text
with a minimum of effort.
All editing can be accomplished by using only a few simple commands; or
the user may select any of a large set of sophisticated commands such as character string searching,
command repetition, conditional commands, programmed editing, and text block movement.
description of TECO only the basic commands are described.
In this
If the user requires information about
the more advanced uses of TECO, he can refer to the rEeO manual in the DECsystem-10 User'.
Handbook.
rECO is a character-oriented editor. One or more characters in a I ine can be modified without
retyping the rest of the line. Any sort of document can be edited: programs written in FORTRAN,
COBOL, MACRO-la, or any other language; memoranda; specifications; and other types of
arbitrarily formatted text.
TECO does not require that I ine numbers or any other extraneous informa-
tion be associated with the text.
1.1
GENERAL OPERATING PROCEDURE
TEeo operates on ASC II data fi les.
A fi Ie is an ordered set of data on some peripheral dey ice.
In the case of TECO, a data fi Ie is some type of document. An input fi Ie may be a named fi Ie on
disk or DECtape, a file on magnetic tape, a deck of punched cards, or a punched paper tape.
An
output file can be written onto any of these same devices. The input file for a given editing operation is the fi Ie to which the user wishes ~o make changes.
fi Ie, there is no input fi Ie. The output
of the input file.
n Ie
If the user is using TECO to create a new
is either the newl y created fi Ie or the edited version
An output file is not required if the user wishes merely to examine a file without
making any changes.
In general, the process of editing praceeds as follows.
edit and then reads in a "page" of text.
a single sheet of paper.
Form feeds are used to separate a document into pages. On input, TECO
interprets form feeds as end-oF-page indiicators.
divided into pages.
The user first specifies the fi Ie he wishes ta
A page is normally an amount of text that is intended for
It is not required, however, that a document be so
If a form feed is no~ encountered, TEeO simpl~/ reads as much text as will
reasonably fit into its editing buffer.
For the purposes of this document, the word ~ is used to
mean the segment of text in TECO's editing buffer.
1-1
When a page has been read inta the buffer, the user can modify this text by using the various editing
commands. When he has finished editing the page, he outputs it and reads in the next page. This
process continues unti I, after the last page has been output, the user closes the output fi Ie.
If there
are several pages where no editing is required, there are commands which may be used to skim over
them.
1. 2
INITlALlZATIOt~
The two main uses of Tf.CO are (1) to create a new disk fi Ie, and (2) to edit an existing disk fi Ie.
These are the onl y uses of TECO described in this document.
In particular, the use of TEeO
with devices other than disk is not described. The beginner can get around this limitation by using
PI P to transfer fi les to and from disk.
(Refer to the PI P manual in the DECsystem-10 Users
Handbook for information about PI P.)
The two main uses of rECO are so common that there are direct monitor commands to initialize
TECO for executing them.
The command
. MAKE
filename.ext)
is used to initialize TECO for creating a new disk file.
to the new file.
Filename.ext is the name that the user gives
The filename can be from one to six alphanumeric characters. This is followed
(optionally) by a period (.) and a filename extension of from one to three alphanumeric characters.
The most commonly used filename extensions are:
.FOR
.CBl
. MAC
for FORTRAN-l0 source programs
for COBO l source programs
for MACRO-10 source programs
The MAK E command opens a new disk file to receive output from TECO and gives it the name specified by the user. Once the fi Ie has been opened it is then actually created by using the insert and
output commands, which are explained in sections 2.5 and 2.6 of this document.
The command
.!.
TECO
filename.ext)
is used to initialize TECO for editing an existing disk file, named filename.ext.
The filename and
fi lename extension must be exactly the same as those of the fi Ie that ;s to be edited. The TECO
command opens the specified fi Ie for input by TECO and opens a new file, with a temporary name,
for output of the edited version. When output of the new version is completed, the original version
of the file is automatically renamed filename.BAK, and the newly edited version is given the name o.f
the original file.
The filename extension. BAK is used for backup files.
1-2
After TEeO has been initialized for a particular job, it responds by typing an asterisk (*). The
asterisk indicates that TEeO is ready to accept commands; it is typed at the beginning of TEeO's
operation and at the completion of execution of every command string.
Examples:
This command initializes TEeO for creation
of a new disk file called EARNNG .FOR.
The extension FOR is used because the fi Ie.
Is to be a FORTRAN-10 source file.
.:.. MAKE EARNNG.FOR)
*
!..
TECO FORLIB .MAC)
This command initializes TECO for editing
the existing disk file FORLIB .MAe. At the
completion of editing, TECO automatically
changes the name of the original version of
FORLIB .MAC to FORLIB .BAK and gives the
name FORLIB .MAC to the new version.
*
NOTE
The TEeO command cannot be used to edit a file which
has the filename extension .BAK. To edit a backup file
the user must first rename the backup file. For example,
to edit the file FORLIB .BAK the user should proceed as
follows:
.:.. RENAME FORLlB.OLD=FORLIB .BAK)
.:.. TECO
FORUB .OLD)
*
1.3
SPECIAL SYMBOLS USED IN THIS DOCUMENT
Table 1-1
Special Symbols
Symbol
)
CD
tC
Character Represented
Comment
Carriage Return
Whenever the RETURN key is typed,
TECO automaticall y appends a line
feed to the carriage return.
Altmode
On most terminals, the altmode key
is 'abeled "ALTMODE", but on some
it is 'abeled "ESC" or "PREFIX".
Since the altmode is a non-printing
character, TECO indicates that it
has received an altmode type-in by
echoing a dollar sign (S).
Control C
This character is typed by typing
the letter C while holding down the
CTRL key. Other control characters
are ~epresented in similar fashion.
-
---
1-3
Table 1-1 (Cont)
Special Symbols
Symbol
Comment
®
(FORM)
Form Feed
Form feed is typed by typing
(control l).
1
line Feed
This symbol is used only when a line
feed is explicitly typed. It is not
used for the line feed which is
automatically assumed when a
carriage return is typed.
Tab
Tab is typed by typing
(control I).
II
Space
This symbol is used occasionally
for emphasis.
@
Rubout
This key is used to null ify a
character erroneously typed in a
command string. Its use is expained fully in Section 1.5.
~
1.4
Character Represented
®
GENERAL COMMAND STRING SYNTAX
IECO commands are usually given by typing the one- or two- letter nome of the command.
many of the commands toke arguments.
However,
Some typical examples are shown below, to give the reader
an idea how TECO commands look. These commands are fully explained later in the manual.
l
PW
ISAMPlEG)
3K
TECO commands may be given one at a time.
However, it is usually more convenient to type, in a
single command string, several commands that form a logical group. An example of a command string
is shown below.
~IHEADING G)NTAG:G)2lT G) G)
A command string may be typed after TECO indicates its readiness by printing an asterisk. Command
strings are formed by merely writing one command after another. Command strings are terminated by
typing two consecutive altmodes.
Execution of the command string begins only after the double altmode has been typed.
At that point
each command in the string is executed in turn, starting at the left. When all commands in the string
have been executed, TeCO prints another asterisk, indicating its readiness to accept another command.
1-4
If some command in the string cannot be executed because of a command error, execution of the
,command string stops at that point, andl an error message is printed. Commands preceding the bod
command are executed. The bod command and those following it are not executed.
1.5
ERASING COMMANDS
Typographical errors, if discovered while typing a command string, may be "erased" by use of the
rubout key. This process is best explained by an example.
* 3LK ILEIF
ERICXON
After typing this much of the command string, the user discovers that he has misspelled the name
"Ericson." To nullify his error, he types three successive rubouts. As he does this, TECO responds
by retyping the characters which are being rubbed out.
~3lKllEIF
ERICXON
@~@
Q@ ~
Of course, rubout is a non -print ing character so the actual Iine looks I ike this:
*
3lKIlEIF ERICXONNOX
Once he has rubbed out the bad character, the user continues the command string from the last
correct character.
~ 3lKIlEIF ERICXONNOXSONCDOlTC!X!)
The actual function of the rubout character is to delete the lost typed character in the command string.
Consequently, if the bad character is n01r the lost in the string, all characters back to that point must
be deleted. Rubout· characters do not enter the command string.
An entire command string may be erased, if it has not yet been terminated, by typing two successive
t G (control G) characters.
Example:
* 3lKIlIEF ERICXON tG tG
1.6
tG tG causes the entire command
string to be rejected. TECO types a
new asterisk and awaits a new command.
COMMAND ARGUMENTS
There are two types of arguments for TECO commands. Some commands require numeric arguments
and some require alphanumeric (text) arguments.
1-5
Numeric arguments, and also all numeric type-outs by
reco,
are decimal integers.
Numeric argu-
ments always precede the command ta which they apply. A typical example af a command taking
a numeric argument is the command to delete three characters: "30".
Alphanumeric arguments are textual arguments meant to be interpreted os ASCII code by TECO.
Alphanumeric arguments always follow the command to which they apply, and they must always be
terminated by an a It mode • Examples of alphanumeric arguments are (1) text to be inserted, and (2)
character strings to be searched for.
Example:
~ ISOtvETHING
®®
The argument is "SOMETHING" .
As shown in the above example, the altmode used to terminate an alphanumeric argument may also
serve as one of the two altmodes necessary to terminate a command string. Any ASCII character
except null, altmode, and rubout may be included in an alphanumeric argument.
1-6
CHAPTER 2
TECO COMMANDS
2. 1 INPUT COMMANDS
The Y (yank) command first clears the editing buffer and then reads the next page of the input fi Ie
into the buffer.
A single Y command is automatically performed by the command
• TECO
filename.ext)
so that when editing with this command the first page of the input file is automatically read in before
TECO prints the first asterisk.
The Y command may be used to delete entire pages of a file, since the editing buffer is completely
cleared before the input is performed.
The A (append) command reads in the next page of the input file without clearing the current contents
of the editing buffer. This command is used to combine several pages of a document. When the A
command is used, the form feed separating the page alreocly in the buffer and the page to be read in
is removed'. Thus after the A command the two pages are combined into one.
If the editing buffe-r does not have enough room to accommodate an A command which has been given,
TECO automatically expands its buffer and then executes the A command. The user is notified of this
action by a message of the following form
[3K CORE]
If sufficient core is not available to allow buffer expansion, the user is notified by an error message.
NOTE
On either an A or a Y command the form feed terminating the page to be read in is not actually read into
the buffer. It is removed on input and a single form
feed is appended to the end of the buffer when the
buffer is output.
2-1
Examples:
.!.
TEeo REPORT .CBl">
*
*
This command deletes the entire contents of
the buffer and then reads in the next page of
the input file.
~AA(!)(!)
*
Read the next two pages of the input file into
the buffer, combining them with the page
already in the buffer.
~A<!XD
(41< CORE]
*
2.2
This command, as part of the process of
initializinll TEeO for editing the disk file
REPORT .eBl, automatically clears the
buffer and then reads in the first page of
the file.
The buffer is expanded as required by the A
command. In most cases this message need be
of no concern to the user. It is important
only if the system is low on core and does
not have swapping capabi lity.
BUFFER POINTER POSITIONING
Since TEeO is a character-oriented editor, it is very important that the user understand the concept
of the buffer pointer. The position of the buffer pointer determines the effect of many of the editing
commands.
For example, insertion and deletion always take place at the current position of the
buffer pointer.
The buffer pointer is simply a movable position indicator.
It is always positioned between two char-
acters in the editing buffer, or before the first character in the buffer, or after the last character in
the buffer.
It is never positioned "on" a particular character, but rather before or after the character.
The pointer may be moved forward or backward over any number of characters.
The J command moves the buffer pointer to the beginning of the buffer, i. e., to the position immediatey
before the first- character in the buffer.
The ZJ command moves the pointer to the end of the buffer, i. e., to the position following the last
character in the buffer.
The C command advances the pointer over one character in the buffer. The C command may be preceded by a (decimal) numeric argument. The command nC moves the pointer forward over n characters.
(The pointer cannot be advanced beyond the end of the buffer.)
The R command moves the pointer backward over one character in the buffer. This command may also
be preceded by a numeric argument. The command nR moves the pointer backward over n characters.
(The pointer cannot be moved backward beyond the beginning of the buffer.)
2-2
The L command is used to advance the buffer pointer or move it backward, on a line-by-line basis.
The L command takes a numeric argument, which may be positive, negative, or zerC", and is under"
stood to be one (1) if omitted.
The action of the L command with various arguments is best explained in a more concrete way.
Suppose the buffer pointer is positioned at the beginning of line b, or at some position within line b.
The command L, or lL, advances the pointer to the beginning of line b+l, i.e., to the position
following the line feed which terminates line b.
The command nL, where n >0, advances the pointer to the beginning of line b+n.
The command OL moves the pointer to the beginning of line b.
If the pointer is already at the be-
ginning of line b, nothing happens.
The command -L moves the pointer back to the beginning of line b-l .
The command -nL moves the pointer bock to the beginning of line b-n.
NOTE
After execution of a Y command, the buffer pointer is
always positioned before the first character in the
buffer. (The Y command automatically executes an
implicit J command.) The A command does not change
the position of the buffer pointer.
In examples, the position of the buffer pointer is often
represented in this manual by the symbol t just below
the I ine of text.
Examples:
~J3LCDCD
*
~ ZJ-2L CD CD
*
*
* OL2R
*
This moves the pointer to the beginning of the
next to last line in the buffer.
Advances the pointer to the position following
the fourth character in the next line.
CDCD
ABCDEF
t
The J command moves the pointer to the beginning
of the first I ine in the buffer. The 3L command
then moves it to the beginning of the fourth line.
OL moves the pointer back to the beginning of
the I ine it is cu~·rently on. Then 2R moves it back
over the carriage return-line feed pair which
terminates the preceding line.
In this example of text stored in the buffer, the
position of the buffer pointer is shown to be
between Band C.
2-3
2.3
TEXT TYPE-oUT
Various parts of the text in the buffer can be typed out for examination. This is done by use of the
T command. Just what is typed out depends on the position of the buffer pointer and the argument
given. The T command never moves the buffer pointer.
The command T types out everything from the buffer pointer through the next line feed.
pointer is at the beginning of a line, the command T causes that I ine to be typed out.
Thus, if the
If the pointer
is in the middle of a line, T causes the portion of the I ine following the pointer to be typed.
The command n T (n >0) is used to type out n lines, i. e., everything from the buffer pointer through
the nth line feed following it.
The command OT types out everything from the beginning of the current I ine up to the buffer pointer.
This is useful for determining the position of the pointer.
The command HT types out the entire contents of the buffer.
The user, especially one new to TECO, should use the T command often, to make sure the buffer
pointer is where he thinks it is.
During execution of any T command, the user may stop the terminal output by typing the
to
(control 0) character. This command causes TECO to finish execution of the command string,
omitting all further type-out. The"
to
command does not carryover to the next command string.
Examples:
~OlT
CD CD
ENTIRE "LINE TYPED
*
* OTT
CD CD
ENTIRE LINE TYPED
*
* 2T
CDCD
EF
GHIJKl
*
This command string is used to move the pointer
back to the beginning of a line and then type out
the entire line. It is frequently used after insert ion and search commands.
This command string causes the entire line to
be typed without moving the pointer. It is useful
after insertion and search commands when it is not
convenient to move the pointer bock to the
beginning of the line.
If the buffer contains the text below with the
pointer between D and E,
ABCDtEF)
1
GHIJKl ) 1
MNOPQR) 1
this command causes the typeout shown .
.. ABCD" is not typed because these characters precede the pointer. MNOPQR is not typed because
these characters follow the second Iine feed.
2-4
2.4
DELETION COMMANDS
Characters are deleted individually by using the 0 command. The command 0 deletes the character
immediately following the buffer pointer. The command nO, where n >0, deletes the n characters
immediately following the pointer. The commands -0 and -nO delete the character or the n
characters, respectively, which immediately precede the buffer pointer.
Lines are deleted using the K command. The K command may be preceded by a numeric argument,
which is understood to be 1, if omitted. The command nK (n> 0) deletes everything from the
current position of the pointer' through the nth line-feed character following the pointer. The
command HK deletes the entire contents of the buffer.
At the conclusion of a D or K t:ommand the buffer pointer is positioned between the characters which
precede and follow the deletion.
Examples:
The edi ting buffer contains the following three Iines of text,
and the pointer is positioned between the G and H.
ABCDEFGtHIJKLM ) ,
NOPQRSTUVWXYZ) , .
1234567890 ) ,
~ 40
CDCD
Delete HIJK.
*
Delete G.
*
~ -3D
*
CDCD
Delete HIJKLM) but do not delete the line
feed at the end of the fi rst line.
*
*K
Delete EFG.
CDCD
*
~2Kl0D
*
CD CD
Delete HIJKLM) '.
Since the carriage return and Iine feed at the end
of the first line are deleted, the text in the buffer
after this command would be:
ABCDEFGNOPQRSTUVWXYZ ) '
1234567890 .J ,
This would leave the buffer containing only
ABCDEFG) ,
2-5
* OlK
*
* l2K
*
* HK
*
2.5
CVCV
This is the command string that is required to
kill {delete} the entire first line.
CVCV
This kills the last two lines.
K ill the entire buffer.
CVCV
INSERTION COM~ND
The only insertion command is the I command. The ASCII text that is to be inserted into the buffer is
typed immediately after the letter I. The text to be inserted is terminated by 'an altmode.
Any ASCII character except null, altmode, and rubout may be included in the text to be inserted.
Specifically, spaces, tabs, carriage returns, form feeds, line feeds, and control characters are all
allowed.
If a carriage return is typed in an insertion, it is automatically followed by a Iine feed.
The text to be inserted is placed in the buffer at the position of the buffer pointer, i. e., between
the characters. At the conclusion of the insertion command the buffer pointer is positioned at the
end of the insertion.
Any number of lines may be inserted with a single I command.
For the user's protection, however,
no more than 10 to 20 lines should be inserted with each I command.
Examples:
If the buffer contains ABCD,EF)
~
*
with the pointer between D and E, the command
IXYZ CV CV
*
* II
produces ABCDXYZtEF) 1
produces
ABC 0 ) 1
t EF ) 1
produces
ABCD I
t EF )
..
~ 3RI~ CV4CI~ CVCV
produces
A~ BCDE~ t F ) I
*
~ I ffi'RM)
CVs
*
This command is used to separate the page in the
buffer into two pages. Both pages, however,
remain in the buffer. They are not actually
separated unti I output.
2-6
* JILINE ONE)
LINE TWO)
LINE THREE)
This example shows insertion of several Iines of
text ot the begi nn ing of the buffer.
CD CD
*
~KI)
This is the command string used to delete the
tail of a line without removing the carriage
return-line feed at the end of the line. If the
buffer contains
CD CD
*
AB.CD) ,
EFGH) ,
This command will produce
AB),
f EFGH ),
2.6
OUTPUT COMMANDS
J'he command P causes (1) the entire contents of the editing buffer to be output to the output fi Ie
and (2) an impl icit Y command to be performed which reads in the next page of the input fi Ie. This
command is used after editing of a given page is complete and the user is ready to move on to the
next page.
The P command may be used with a posItive numeric argument to skim over several pages. Specifically, the nP command causes the n consecutive pages of the input file, starting with the page in the
editing buffer, to be output, and then tine n+1st page to be yanked in.
The PW command merely outputs the page currentl y in the editing buffer.
It does not clear the
buffer, it does not read in any more texl', and it does not move the buffer pointer. This command is
used when creating a new fi Ie.
It is also used to output the last page of a file.
If the buffer is empty, the PW and P commands have no effect.
The EF command must be used to close the output file after all output to it is complete. EF is
normally used after the PW command which outputs the last page of the file.
Examples:
~ PWEF
*
~PT
CDCD
CDCD
FIRST LINE
This is the command string usually used to
close out a fi Ie when the lost page of the fi Ie
is in the buffer.
This command string outputs the current page,
reads in the next page, and then types the
first Iine of the new page.
*
2-7
If, for exomple, page 6 of a document is in the
editing buffer, this command causes poges 6
through 13 of the document, to be output,
one after the other, and then reads in page 14.
*
2.7
SPECIAL EXIT COMMANDS
The EX command is used to conclude an editing job with a minimum of effort.
Its use is best shown
by an example.
Suppose the user is editing a 30-page fi Ie and suppose that the last actual cha~ge to the fi Ie is made
on page 10. At this point the user gives the command
*EXC!)C!)
.:..
In this case the action performed by TECO is equivalent to the command string 2OPPWEF, with an
automatic return to the monitor at the end. Thus, the action of TECO is (1) to rapidl y move all the
rest of the input file on to the output file, (2) close the output file, and (3) to return control to
the mon i tor.
The EG command is even more efficient. This command performs exactly the same functions as the
EX command, but after that it causes re-execution of the last COMPILE, LOAD, EXECUTE, or
DEBUG command attempted before TECO was called.
For example I suppose the user gives the command
.!..
COMPilE PLOT .F4)
To request compilation'of a FORTRAN source program, but the compiler discovers errors in the code.
The user would then call TECO to correct these errors:
.:.. TECO PLOT. F4)
*
When all the errors are edited, the user exits from TECO with the command
~EG
C!)C!)
This causes the COMPILE command to be executed again on the fj Ie PLOT. F4, after TECO has
fi ni shed output of the fi Ie.
2,"8
Any TECO job may be aborted by using the standard return-to-monitor command: te tc (control C
However, it this command is typed before the output file is closed, the output file
typed twice).
is lost.
If no input or output operations are in progress a single
monitor.
tC
is sufficient to exit from TECO to the
In such a case, the user may reenter TEeO without destroying the job he was previously
executing.
This is illustrated in the following example.
. TECO
SOURCE. MAC)
* ICO MMENTS
* tC
CD CD
A TEeO iob is started .
The user exits to perform a few simple monitor
commands .
. DEASSIGN lPT )
:... DAYTIME)
28-OCT -74
10:34
The user reenters TECO.
is still intact.
:... REE)
*
2.8
The previous buffer
SEARCH COMMANDS
In many cases the simplest way to position the buffer pointer is by using a character string search.
A search command causes TECO to scan through the text unti I a specified string of characters is
found, and then to position the pointer CIt the end of this string.
There are two main search commands.
The S command is used to search for a character string within the editing buffer.
The string to be
searched for is specified as an alphanumerical argument following the S command.
This argument
must be terminated by an a It mode . The character string to be searched for may contain any ASCII
character except null, altmode, or rubout.
The S command may be preceded by a numerical argument n
> 1.
This argument is used to search for
the nth occurrence of a character string. Thus a 2S command searches for the second occurrence of
the particular character string, skipping the first occurrence.
If n is omitted, n
=1
is assumed.
Execution of the S command begins at the position of the buffer pointer and continues to the end of
the buffer.
If the specified character string is not found in this range, an error message is printed and
the buffer pointer is set to the beginning of the buffer.
Examples:
* SA -I B
*
CDCD
This causes the pointer to be positioned after the
B in the first occurrence of the string
A - tab - B past the current position of the pointer.
2-9
* J2SNA~
*
<D <D
• S2O)
TAG:
<D OLT <D<D
TAG:
REST OF LINE
•
This causes the pointer to be positioned after
the second occurrence of the string "NAME" in
the buffer.
This moves the pointer to the positionJ'ust
following the colon in the string' 1 20 'TAG :1' ,
then repositions the pointer to the beginning of
the I ine (lust before the liT AG:") and types out
the entire I ine starting with liT AG:" .
Warning: When attempting a search it is very easy to overlook on occurrence of the search string
preceding the one which the user desires.
For example, he may wont to move the pointer after the
word "ANO" but erroneously position it after a preceding occurrence of a word like "THOUSAND".
For this reason the user, especially the novice, is strongly urged to execute a T command to ascertain
the position of the pointer after each search command.
Example:
<D OTT CD<D
FORtv1AT{l Xc 'WORD')
~ '6 WORD2 <D<D
~ SWORD
Here the user wishes to insert" 6 WORD2"
after "WORD". He wisely types out the line
to make sure he is at the right place, before
inserting' IWOR 02 11 •
*
The other principle search command is the N command. The difference is that on S search ends at
the end of the current buffer, whereas on N search does not. An N search begins Iike an S search,
but if the character string is not found in the current buffer, an automatic P command is executed.
The current page is outputted, the next page read in, and the search continued on the new page.
This process,continues until either the string is found or the input file is exhausted.
If the N search does find the specified character string, the pointer is positioned at its end.
If the string is not found, on error message is generated.
amount of delay.
In this case the user caused himself a fair
If on N search foils, the user must close the file with on EX command, then reopen
it and try the N search again with a character string that can be found.
The user is strongly urged to
be careful when typing search character strings. Remember also that a search string must be terminated
with on altmode.
2-10
Example:
I
~NSTRING -3D
C!)OO
?SRH CANNOT FIND uSTRING-3D"
~EX
.!..
C!)OO
TECO filename. ext )
* NSTRING
00 -3D CDC!)
Here the user meant to search for the
character string "STRING", ond to
delete the last three characters of the
string. However, he forgot to terminate
the search string with an altmode and
this caused the unsatisfied search request
error message (15 RH) .
*
Version 23 TECO
2-11
May 1972
CHAPTER 3
ERROR M:SSAGES
When TEeO encounters an illegal command or a command that for any other reason cannot be executed,
on error message is printed on the user's terminal. Such messages contain a three-character code of the
form 1aaa and a one-line description of the error.
To get more information about the error, the user can type a slash (/) immediately after he receives
the error message. TEeO wi II type on additional message that describes the error in more detai I.
All three parts of the error messages from TECe are given in Table 3-1.
When an error message is generated, the command to which it refers is not executed, the remainder
of the command string is ignored, and TECO retruns to the idle state by typing an asterisk and
awaiting a new command string.
The novice user is especially warned that there are a great many TEeO commands that have not been
described in this introductory material. Almost every letter of the alphabet and many of the special
characters have meanings as TECe commands. Hence, the user should be careful when typing
command strings. The beginner should plrobably stick to relatively short command strings.
In the following table, all TECO error messages are listed, even though some of them refer to the
more advanced commands not described in this manual. Error messages referring to the advanced
commands wi II probably be encountered by the user of this introductory material only if he has typed
an unintended command letter.
The complete set of TEeO commands is fully described in the TECe manual in the DECsystem-10
Users Handbook. Since most editing can be done using only the basic commands covered in this introductory material, most users should be able to get along without the more advanced description for
some time. The novice should gain complete mastery of the basic commands before attempting to use
any of the advanced commands.
Version 23 TEeO
3-1
May 1972
Table 3-1
TECO Error Messages
?ARG
1)
2)
3)
4)
Improper Arguments
The followin~ argument combinations are illegal:
,
(no argument before comma)
m,n,
(where m and n are numeric terms)
H,
(because H=B I Z is already two arguments)
,H
(H following other arguments)
?BAK
Cannot Delete Old Backup File
Failure in rename process at close of editing lob initiated by
an EB command or a TECO command. There exists an old
backup file filnam. BAK with a protection<nnn> such that it
cannot be deleted. Hence the input file filnam.ext cannot
be renamed to "filnam.BAK". The output file is closed with
the filenam "nnnTEC. TMP", where nnn is tne user's job
number. The RENA~ UUO error code is nne
?COR
Storage Capacity Exceeded
The current operation requires more memory storage than
TECO now has and TECO is unable to obtain more core
from the monitor. This message can occur as a result of
any ane of the following things:
1)
2)
3)
command buffer overflow while a long command
string is being typed,
Q-register buffer overflow caused by on X or
[ command,
editing buffer overflow caused by an insert command
or a read command.
?COS
Contradictory Output Switches
The GENLSN and SUPLSN switches may not both be used
with the same output file.
?EBD
EB with Device dev Is Illegal
The EB command and the TECO command may be specified
only with file structured devices, i. e., disk and DEC tope •
?EBF
EB with Illegal File filnam.ext
The EB command and the TECO command may not be used
with a file having the filename extension ". BAK" or with
a file having the nome "nnnTEC.TMP". Where nnn is the
user's job number, the user must either use on ER-EW
sequence I or rename the fi Ie.
?EBO
EB, EW, or EZ Before Current EB Job Closed
After an output fi Ie has been opened by a TECO command
or an EB command, no further EB, EW, or EZ commands
may be given until the current output file is closed.
?ESP
ES Illegal Because of File filnam.ext Protection
The file filnam.ext cannot be edited with on EB command
or a TECO commood because it has a protection <nnn> such
that it cannot be renamed at close time.
Venion 23 TECO
3-2
May 1972
Table 3-1 (Cont)
rECO Error tvtessages
?fEE
Unable to Read Error tvtessage Fi Ie
An error, whose code was typed previous to this error
message!, has occurred, and while TECO was trying to find
the proper error message in the error message fi Ie, one of
the following errors occurred: 1) the error message fi Ie,
TEeO.ERR, could not be found on device SYS:, 2) an input
error occurred while TEeO was reading the file TECO.ERR,
3) The error message corresponding to that error code is
missing from TEeO.ERR, 4) the user's TECO job does not
currently have enough room for a buffer to read the error
message into, and no more core can be obtained from the
monitor p 5) for some strange reason device SYS: could not
be initial ized for input.
~-------------------------------------------------------------------------------------
EM with Illegal Argument nn
The argument n in an nE M command must be greater than zero.
?EMA
b--------------------------------------------------------------~-----------------------~
?EMD
EM with No Input Device Open
EM commands apply only to the input device, and so should
be preceded by an ER (or equivalent) command. To position
a tope for output, that unit should be temporarily opened
for input while doing the EM commands.
b-----------------------------------------------------------------------------------?ENT-OO
Illegal Output Filename IIfilnam.ext"
ENTER DUO failure O. The filename "filnam.ext" specified
for the output file cannot be used. The format is invalid.
~--------------------------------~-------------------------------------------------
-01
Output UFD dev: [pi, pg] Not Found
ENTER UUO fai lure 1. The fi Ie filnam. ext [pi, pg] specified
for output by an EW, El, or MAKE command cannot be
created because there is no user file directory with proiectprogrammer number [pi, pg] on device dev.
-02
Output Protection Fai lure
ENTER LJUO failure 2. The file filnam.ext[pl,pg] specified
for output by an EW, El, EB, MAKE, or TEeO command
cannot be created either because it already exists and is
write-protected <nnn> against the user, or because the UFD
it is to be entered into is write-protected against the user.
-03
Output File Being Modified
ENTER UUO failure 3. The file filnam.ext specified for
output by an EW, El, EB, MAKE, or TECO command cannot
be created because it is currently being created or modified
by another iob.
~-------------------------------------------------------------------------------------
Output UFD or RIB Error
ENTER UUO failure 6. The output file filnam.ext 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 EW, EB, or TEeO command, but if the error
persists, it is impossible to proceed. Notify your system
manager.
r-------------------------------------------------------------------------------------14
Version 23 TECO
No Room or Quota Exceeded on dev:
ENTER UUO failure 14. The output file filnam.ext cannot be
created because there is no more free space on device dev:, or
because the user's quota is already exceeded there.
3-3
May 1972
Table 3-1 (Cont)
TEeO Error Messages
-15
Write lock on dev:
ENTER UUO failure 15. The output file filnam.ext cannot·be
created because the output fi Ie structure is write -locked.
-16
Mon itor Table Space Exhausted
ENTER UUO failure 16. The output file filnam.ext cannot be
created because there is not enough table space left in the
monitor to allow the ENTER. The user may try repeating the
EW, EB, or TEeO command, but if the error persists he wi II
have to wait until conditions improve.
~-----------------------------------------------------------------------------------
-23
Output SFD not Found
ENTER UUO failure 23. The output file filnam.ext cannot be
created because the sub-file-directory on which it should be
ENTERed cannot be found.
-24
Search list Empty
ENTER UUO failure 24. The output file filnam.ext cannot be
created because the user' 5 fi Ie structure search I ist is empty.
-25
Output SFD Nested too Deeply
ENTER UUO fai lure 25. The output fi Ie fi Inam. ext cannot be
created because the specified SFD path for the ENTER is
nested too deeply.
-26
No Create for Specified SFD Path
ENTER UUO failure 26. The output file filnam.ext cannot be
created because the specified SFD path for the ENTER is set
for no creation.
-on
ENTER Fai lure nn on Output Fi Ie fi Inam. ext
The attempted ENTER of the output fi Ie fi Inam. ext has fai led
and the monitor has returned an error code of nn. This error
is not expected to occur on an ENTER. Please send the TTY
printout showing what you were doing to DEe with an SPR form.
?EOA
nEO Argument Too Large
The argument n given with an EO command is larger than the
standard {maximum} setting of EO=n for this version of TEeO.
This must be an older version of TEeO than the user thinks he
is using; the features corresponding to EO=n do not exist.
?FNF-OO
Input File filnam.ext Not Found
LOOKUP UUO failure O. The file filnam.ext specified for
input by an ER, EB, or TEeO command was not found on the
input device dev.
-01
Input UFO dev: [pi, pel Not Found
LOOKUP UUO failure 1. The file filnam.ext[pi,pg] specified
for input by on ER, EB, or TECO command cannot be found
because there is no User File Directory with pr01ect-programmer
number [pi, pgl on device dev.
-02
Input Protection Fai lure
LOOKUP UUO failure 2. The file filnam.ext [pi, pg] specified
for input by on ER, EB, or TECO command cannot be read
because it is read-protected <nnn > against the user.
Version 23 TECO
3-4
May 1972
Table 3-1 (Cont)
TECO Error Messages
..-----------------_._------------------------------06
Input UFD or RIB Error
LOOKUP UUO failure 6. The input file filnam.ext cannot be
read because a bod directory block was encountered by the
monitor while the LOOKUP was in progress. The user may try
repeatiing the ER, EB, or TECO command, but if the error
persists all is lost. Notify your system manager.
~----------------.---------------------------.------
-16
~nitor Table Space Exhausted
LOOKUP UUO failure 16. The input file filnam.ext cannot be
read because there is not enough table space left in the moni tor
to allow the LOOK UP. The user may try repeating the ER, EB,
or TECO command, but if the error persists he wi II have to wait
until system conditions improve.
i-----------------...:..-----------.:------------------------------------23
Input SFD not Found
LOOK U P UUO fai lure 23. The input fi Ie fi Inarn. ext cannot be
found because the sub-file-directory on which it should be
looked up cannot be found.
-
-24
Search li st Empty
LOOK U P UUO fai lure 24. The input fi Ie filnam. ext cannot be
found because the user's fi Ie structure search Iist is empty.
r----,---------------25
--------------------------
Input SFD Nested too Deepl y
LOOKUP UUO failure 25. The input file filnam.ext cannot be
found because the specified SFD path for the LOOKUP is
nested 1'00 deeply.
~-------------------'----------------------.---""-------
-nn
LOOKUP Failure nn on Input File filnam.ext
The attempted LOOKUP on the Input file filnam.ext has
foiled and the monitor has returned on error code of nn. This
error is not expected to occur on a LOOKUP. Please send
the TTY printout showing what you were doing to DEC with
an SPR form.
~--------------------------------------------------------------------------
?FUL
Device dev: Directory Full
ENTER UUO failure n. The file filnam.ext specified for
output by on EW or MAK E command cannot be created on
DECtape dev because the tope directory is full.
?IAB
Incomplete < ... > or ( •.. ) in Macro
A macro) contained in a Q-register and being executed by on M
command contains on iteration that is not closed within the
Q-register by a >, or a parenthetical expression that is not
closed within the Q-register by 0).
?ICE
Illegal Control-E Command in Search Argument
A 'search argument contains a
command that is either
not defined or incomplete.
®
t---------------------------------...::..-.---------------------------?ICT
Version 23 TECO
Illegal Control Command f < char> in text Argument
In order to be entered as text in an Insert command or search
command, all control characters (t@ - tH and tN - t -) must
be preceded by tR or tT. Otherwise they are interpreted as
commands. The control character II t <char>" is on undefined
text argument control command.
3-5
May 1972
Table 3-1 (Cont)
TECO Error Messages
?IDV
Input Device dev Not Available
Initialization failure. Unable to initial ize 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.
?IEC
Illegal Character ' I < char> " After E
The only commands starting with the letter E are EB, EF, EG,
EH, EM, EO, ER, ET, EU, EW, and EZ. When used as a
command (i .e., not in a text argument) E may not be followed
by any character except one of these.
?IEM
Re-Init Failure on Device dev After EM
Unable to re -in itial i ze 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.
?IFC
Illegal Character "<char>" After F
The only commands starting with the letter Fore FS 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.
?IFN
Illegal Character "<char>" in Filename
File specifications must be of the form dev:filnam.ext[m,n]
where dev, filnam, and ext are alphanumeric, and m and
n are numeric. No characters other than the ones specified
may appear between the
ER, EW, or EZ command and
the altmode terminator (\!)).
CD
*,
?ILL
Illegal Command <char>
The character "<char >" is not defined as a valid
TECO command.
?ILR
Cannot Lookup Input Fi Ie fi Inam. ext to Rename It
Failure in rename process at close of editing iob initiated by on
EB command or a TECO command. Unable to do a LOOKUP on
the original input fi Ie dev:fi Inam. ext in order to rename it
"filnam.BAK". The output file is closed with the nome
"nnnTEC. TMP", where nnn is the user's lob number. The
LOOKUP UUO error code is nne
?I N P-nnOOOO
Input Error nnOOOO on File filnam.ext.
A read error has occurred during input. The input fi Ie fi Inam. ext
has been released. The user may try again to read the fi Ie, but
if the error persists, the user will have to return to his backup
fi Ie. The input device status word error flags are nnOOOO.
(Note: This number represents the I/O status word (rh) with bits
22-35· masked out. )
(040000 -- block too large).
(100000 -- parity or checksum error).
(140000 -- block too large and parity t:rror).
(200000 -- device error, data missed).
(240000 -- block too large and device error).
(300000 -- parity error and device erro,).
(340000 -- block too lorge, parity error, and
device error).
Version 23 TECO
3-6
May 1972
Table 3-1 (Cont)
TECO Error Messages
r--------------------------------------------------------------------'-----------(400000 -- improper mode).
(440000 -- block too large and improper mode).
(500000 -- parity error and improper mode).
(540000 -- block too large, parity error, and
improper mode).
(600000 -- device error and improper mode).
(640000 -- block too large, device error, and
improper mode).
(700000 -- parity error, device error, and
improper mode).
(740000 -- block too lorge, parity error, device
error, and improper mode).
?IOS
-----··--·------1I
Illegal Character "<char)1I in I/O Switch
The only val id characters in switches used with fi Ie selection
~----__-------------------c-o-m--m-a-n--d-s-a-r-e-t-h-e-a-l-p-h-a-b_e_ti_c_c_h_ar_a_c_t_e_rs_.________________________
?IQC
Illegal cammand II <char)
The only valid "commands are "G, "l, liN, liE, lie, "A,
"0, "V, "W, liT, "F, "5, and "U.
?IQN
Illegal Q-register Name "<char)1I
The Q--register nome specified by a 0, U, X, G, %,
M, [,], or * command must be a letter (A through Z)
or a digit (0 through 9).
l
t--------------------------------------------------------- --,--,---?IRB
Cannot Rename Input Fi Ie fi Inam. ext to fi Inam. BAK
Failure in rename process at close of editing iob initiated
by on EB command or a TECO command. The attempt ta
rename the original input file filnam.ext to the backup
filenan,le "filnam.BAK" has foiled. The output file is
closed with the nome "nnnTEC. TMP", where nnn is the
userls i,ob number. The RENAME UUO error code is nn.
?IRN
Cannot RE-Init Device dev for Rename Process
Fai lure in rename process at close of editing job initiated by
on EB command or a TECO command.
Cannot reinitialize the original input device dev in order
to rename the input file filnam.ext to Ilfilnam.BAK". The
output file is closed with the nome "nnn TEC. TMP", where
nnn is the user ls job number.
?ISA
n Argument with Search Command
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 O.
?MAP
Missin9l I
In attempting to execute a conditional skip command (a I I
command whose argument does not satisfy the required condition)
no I command closing the conditional execution string con be
found. Note: nil .•. I strings must be complete within a single
macro level.
Version 23 TECO
3-7
May 1972
Table 3-1 (Cont)
TECO Error Messages
?MEE
Macro Ending with E
A command macro being executed from a Q-register ends with
the character II E" . This is an incomplete command. E is the
initial character of an entire set of commands. The other character of the command begun by E must be in the same macro
with the E.
~---------------------------------------------------------------------------------------
?MEF
Macro Ending with F
A command macro being executed from a Q-register ends with
the character II F" (not an EF). Th is 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 0 Command
The last command in a command macro being executed from
a Q-register is an 0 command with no altmode to mark the
end of the tag-name argument. The argument fo': the 0 command
must be complete within the Q-register.
-----------------------------------------------------------------------------.--------~
?MEa
?MEU
?MIQ
Macro Ending with II
A command macro being executed from a Q-register ends
with the I I character. This is an incomplete command. The
II command must be followed by one of the characters 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
II.
Macro Ending with t
A command macro being executed from a Q-regi~ter ends with
the t character. This is an incomplete command. The
t command takes a single character text argument that must be
in the a-register with the t.
Macro Ending with <char>
A command macro being executed from a a-register ends with
the character II <char >". This is an incomplete command. The
<char> command takes a single character text argument to name
the a-register to which it applies. This argument must be in the
same macro as the < char> command itself.
?MlA
Missing <
There is a right angle bracket not matched by a left angle
brocket somewhere to its left. (Note: an iteration in a macro
stored in a Q-register must be complete within the a-register.)
?MlP
Missing (
Command string contains a right parenthesis that is not matched
by a corresponding left parenthesis.
?MRA
Missing>
In attempting to exit from an iteration field with a ; command (or
to skip over an iteration field with a 0 argument) no > command
closing the iteration can be found. Note: iteration fields
must be complete within a single macro level.
Version 23 TECO
3-8
May 1972
Table 3-1 (Cont)
TECO Error Messages
?MRP
Missing)
The command string contains, within on iteration field, a
parent,hetical expression that is not closed by a right
parenthes is.
?MUU
Macro Ending with t t
A command macro being executed from a Q-register ends with
contro,l- t or t t. This is an incomplete command. The
f f command takes a single character text argument that must
be in the Q-register with the t f •
?NAE
No Argument Before =
The command n= or n== causes the value n to be typed. The
= command must be preceded by either a specific numeric
argument or a command that returns a numeric value.
?NAI
No All'mode after nl
Unless the EO value has been set to 1, the numeric insert
command nl must be immediately followed by altmode.
?NAQ
No Argument Before I I
The II command must be preceded by a single numeric argument
on which the decision to execute the following commands or
skip to the matching I 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.
?NCS
No Command String Seen Prior to *i
The *i command saves the preceding command string in
Q-regi~ter i. In this case no command string has previously
been given.
?NFI
No File for Input
Before issuing an input command (Y or A) it is necessary to open
an inpvt file by use of an ER, ES, or TECO command.
?NFO
No File for Output
Before giving an output command (PW, P, N, EX, or EG)
it is necessary to open on output file by use of on ES, EW,
EZ, MAKE, or rECO command.
?NTQ
No Text in Q -regi ster x
Q-register x, specified by a G or M command, does not
contain text.
?OCT
"8" or "9" in Octal Digit String
In a digit string preceded by
may be used.
?CDV
Version 23 TEeO
to,
only the octal digits 0-7
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.
3-9
May 1972
Table 3-1 (Cont)
TECO Error Messages
?OLR
Cannot Lookup Output File dev:fi Inam. ext to Rename It
Failure in rename process at close of editing job initiated
by an EB command or a TECO command. The special LOOKUP
on the output file fi Inam. ext required for DECtape in order to
rename the file to 'filnam.ext" has failed. The original input
file filnam.ext has been renamed "filnam.BAK", but the
output fi Ie is closed with the name "nnn TEC. TMP", where
nnn is the user's job number. The LOOKUP UUO error
code is nn.
?O UT -nnOOOO
Output Error nnOOOO - Output File nnnTEC. TMP Closed
An error on the output device is fatal. The output fi Ie is
closed at the end of the last data that was successfully
output, It has the filenome "nnnTEC. TMPII, where nnn is
the user's iob number. See Section 4.3 for a recovery
technique. The output device status word error flags are
nnOOOO. (Note: This number represents the I/O status
word (rh) with bits 22-35 mosked out. )
(000000 -- end of tape).
(040000 -- block number too large: device full or
quota exceeded).
(100000 -- parity or checksum error).
(140000 -- block number too large and parity error).
(200000 -- device error, data missed).
(240000 -- block number too large and device error).
(300000 -- parity error and device error),
(340000 -- block number too large, pari ty error,
and device error),
(400000 -- improper mode or device write locked).
(440000 -- block number too large and improper mode),
(500000 -- parity error and improper mode).
(540000 -- block number too large, parity error,
and i mprope r mode).
(600000 -- device error and improper mode).
(640000 -- block number too large, device error,
and improper mode).
(700000 -- parity error I device error, and improper mode).
(740000 -- block number too large, parity error,
device error, and improper mode).
?PAR
Confused Use of Parentheses
A string of the form ( ..• < ... ) has been encountered.
Parentheses should be used only to enclose combinations of
numeric arguments. An iteration may not be opened and
not closed between a left and right parenthesis.
?POP
Attempt to Move Pointer Off Page with J, C, R, or 0
The argument specified with a J, C, R, or 0 command must
point to a position within the current si ze of the buffer, i. e. ,
between 0 and Z, inclusive.
?PPN
Illegal Character" <char>' I in Project -programmer Number
Project-programmer numbers in file specifications must be given
in the form [m, n] where m and n are octal digit strings separated
by a comma. No characters other than the ones specified may
appear between the enclosing brackets.
Version 23 TECO
3-10
May 1972
Table 3-1 (Cont)
TECO Error Messages
?RNO
Cannot Rename Output File nnriTEC. TMP
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 nnnTEC. TMP to the name
"fillnam.ext" originally specified in the fB or TECO
command has failed. The original input file filnam.ext
has been renamed IIfilnam.BAK", but the output file is
closed with the name "nnnTEC. TMP", where nnn is the
user's lob number. 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.
?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 an Iteration
The semicolon command may be used only with a string of ~
commands enclosed by angle brackets, i.e., in an
iteration field.
?SRH
Cannot Find "<text>"
.
A search command not preceded by a colon modifier ond not
within an iteration hos failed to find the specified character
string "<text>". After an S search fails the 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 the N, output, and the buffer cleared. Note
that when this message occurs, the text string printed
includes all control-character commands included in the
search argument.
?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
positfions, not counting extra characters required to
specify a single position.
r------------------------.--------------------------------~-----------.
?TAG
Missing Tag Ixxxi
The tag I xxx I spec ified by an 0 command cannot be found.
This ':ag must be in the same macro level as the 0 command
referenc ing it.
?TAL
Two Arguments with L
The L command takes at most one numeric argument, name Iy,
the number of lines over which the buffer pointer is to be moved.
?TTY
Illegal TTY 1-0 Device
A terrninal may be specified as an input-output device in an
ER, EW, El, or MAKE command only if it is not being used
to control an attached iob, the user's own terminal included.
'----------------------------------------------------------"-Version 23 rECO
3-11
May 1972
Table 3-1 (Cont)
TECO Error Messages
?lICA
Unterminated t A Command
A t A message type-out command has been given, but there is
no corresponding f A to mark the end of the message. t A
commands must be complete within a single command level.
?UFS
Macro Ending with Unte,minateci File Selection Command
The last command in a command macro being executed from a
Q-register is a file selection command (ER, EW, EB, or EZ)
with no altmode to mark the end of the fi Ie spec ifications.
The file selection command must be complete within the
Q-register.
?lIIN
Unterminated Insert Command
An insert command (possibly an @ insert command) has been
given without terminating the text argument at the same
macro level.
?UIS
Undefined I/O Switch "/xxx"
The switch "/xxx" is not defined with either input or output
file selection commonds. The only switches currently defined
for input or output file selection commands are /GENlSN
and /SU PlSN •
?USR
Unterminated Search Command
A search command (possibly an @ search command) has been
given without terminating the text argument at the some
,nacro level.
?UTG
Unterminated Tag
A command string tag has been indicated by a I command,
but there is no correspond ing I to mark the end of the tog.
Togs must be complete within a single command level.
?UUO
Illegal UUO
Internal error. The illegal instruction <Ih,rh> has been
encountered at address nnnnnn. This is caused by either
a TECO bug or a monitor bug. Please give this printout
to your system manager, or submit it to DEC with an SPR.
Version 23 rECO
3-12
May 1972
INDEX
A
C (Cont)
A (appe nd) command, 2- 1
fW (output page), 2-7
R (move po inter backwards by charac ter ), 2- 2
S (search buffer) I 2-9, 2- 10
T (type), 2-4
TECO (initialize file for editing), 1-2
Y (yank nex t page), 2- 1
ZJ (move pointer to end), 2-2
Alphanumeric arguments, 1-6
Altmode symbol (
CD ), 1-3, 1-4
Arguments, command, 1-5
Asterisk (*) usage, 1-3
Control characters, 1-3
B
o
Backup file, 1-3
Buffer, editing, 1-1
o (delete
Buffer poi nter, 2-2
Data file, 1-1
character) command, 2-5
Deletion commands, 2-5
C
Double altmode, 1-4
Combine pages, 2-1
C
(advanc~
E
pointer by character) command, 2-2
Carriage return symbol ( ) , 1-3
Edi ting files, 1-2
C lose files, 1-2, 2-9
Editing process, 1-1
Command error, 1-5
EF (close output file) command, 2-7
Command arguments, 1-5
EG (close file, reexecute monitor command)
command, 2-8
Command string
End of page indicator, 1-1
execution, 1-4
syntax, 1-4
termi nati on, 1-4
Eros i n9 commands, 1-5
Error in command, 1-5
Commands,
Error messages, 3-1
erasi ng, 1-5
input, 2-1
EX (close file) command, 2-8
Execution of command string, 1-4
Commands,
Ex it commands, 2-8
A (append page), 2-1
Extension, filename, 1-2
C (advance pointer by character),2-2
o (delete character), 2-5
EF (close output file), 2-7
F
EG (close file, reexecute monitor command), 2-8
EX (close file), 2-8
Fi Ie creation, 1-1
HK (delete buffer), 2-5
File, definition of a, 1-1
HT (type entire buffer), 2-4
I (insert), 2-6
File nomes, 1-2
J (move pointer to beginning), 2-2
File devices, 1-1
K (delete line), 2-5
L (move pointer by lines), 2-3
Form feed, 1-1
MAKE (make disk file), 1-2
removal, 2- 1
N (search file), 2-10, 2-11
P (output buffer), 2-7
symbol, 1-4
INDEX-l
INDEX (Cont)
P
H
HK (delete buffer) command, 2-5
P (output buffer) command, 2-7
HT (type entire buffer) command, 2-4
Pages, 1- 1, 1- 2
combining, 2-1
reading into buffer, 2-1
I (i nsert) command, 2-6, 2-7
Period (. ) usage, 1-2
PIP program, 1-2
Illegal commands, 3-1
Initialization of TECO, 1-2
Poi nter, buffer, 2-2
Poi nter posi ti on, 2-2
Input commands, 2-1
P'N (output) command, 2-7
Input file devices, 1-1
R
J
J (move pointer to beginning) command, 2-2
R {move pointer backwards by character}
command, 2- 2
Reentry to TECO, 2-9
Rename backup file, 1-3
K
K (delete line) command, 2-5
Rubout key, 1-5
Rubout symbol (
@ ),
L
L (move pointer by lines) command, 2-3
Line feed symbol ( , ), 1-4
1-4
S
S (search buffer) command, 2-9, 2- 10
Search commands, 2-9
Space symbol ( 6), 1-4
M
MAKE (make disk
file~
command, 1-2
Modifying text, 1-2
Stop Teletype output, 2-4
Symbols used in document, t-3
Syntax of command string, 1-4
T (type) command, 2-4
N
N (search file) command, 2-10, 2-11
Numeric arguments, 1-6
Tab symbol
(~
), 1-4
TECO (initialize file for editing) command, 1-2
Teletype output, stopping, 2-4
Termination of command string, 1-4
Opening a file, 1-2
°
Operat ing procedure, 1-1
Output commands, 2-7
Text modification, 1-2
Text typeout, 2-4
Textual arguments, 1-6
Typographical error correction, 1-5
Output file devices, 1-1
y
Y (yank) command, 2- 1
Z
ZJ (move pointer to end) command, 2-2
INDEX-2
DECsyatem-10
Introduction to TECO
(TEXT EDITOR and
Corrector)
DEC-IO~UTECA~A-D
READER'S COMMENTS
NOTE:
This form is for document comments only. DIGITAL will
use comments submitted on this form at the company's
discretion. Problems with software should be reported
on a Software Performance Report (SPR) form.
If you
require a written reply and are eligible to receive
one under SPR service, submit your comments on an SPR
form.
Did you find errors in this manual?
If so, specify by page.
Did you find this manual understandable, usable, and well-organized?
Please make suggestions for improvement.
Is there sufficient documentation on associated system programs
required for use of the software described in this manual? If not,
what material is missing and where should it be placed?
Please indicate the type of user/reader that you most nearly represent.
[] Assembly language programmer
[] Higher-level language programmer
[] Occasional programmer (experienced)
[J
User with little programming experience
[] Student programmer
[] Non-programmer interested in computer concepts and capabilitiel
Name
Date ______________
Organization ______________.______________________________________________________
Street __________________________________________________________________________________
City _______________________
State __________________ Zip Code ________________
or
Country
- - - - - - - - - -00 Not Tear· "'old Here and Tape - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
III II I
mamaama
No Postage
Necessary
If Mailed
In
the
United States
BUSINESS REPLY MAIL
FIRST CLASS PERMIT NO 33 MAYNARD MASS
POSTAGE WILL BE PAID BY ADDRESSEE
SOFTWARE PUBLICATIONS
200 FOREST STREET MRl-2/E37
MARLBOROUGH, MASSACHUSETTS 01752
- - - - - - - -
Do Not Tear - Fold Here and Tape - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- - -
='
U
">