![]() |
![]() HP OpenVMS Systems Documentation |
![]() |
Extensible Versatile Editor Reference Manual
WHAT LINEFormatWHAT LINE DescriptionThe WHAT LINE command shows the current line number, total number of lines in the buffer, and percentage of that position in the buffer. WHAT LINE is useful if you want to know whether to insert a page break or to find out how many lines are in the buffer. The output from WHAT LINE appears in the message window at the bottom of the EVE screen layout. Related CommandsLINE ExampleThe following example shows the output from the WHAT LINE command:
WILDCARD FINDKey
FormatWILDCARD FIND search-pattern Parameter
DescriptionThe WILDCARD FIND command uses wildcard, literal text, or both, to search for a pattern of text. The default is SET WILDCARD VMS. WILDCARD FIND follows the same rules for direction as FIND. If the string is found, EVE puts the cursor at the beginning of the string and highlights the found text. You can edit the found text by using any command or key that works on a range or box, for example, BOX CUT, COPY, FILL, REMOVE, or UPPERCASE WORD (see Table 2-5). If SET BOX SELECT is in effect, the editing operation uses the start and end of the found range as diagonally opposite corners of a box. To cancel the highlighting, move the cursor off the found range or use the RESET command. Related CommandsCHANGE DIRECTION ExamplesTo search for B or b followed by any single character and a T or t on the same line, use the following command:
WRITE FILEKey
FormatWRITE FILE [output-filespec] Parameter
DescriptionThe WRITE FILE command writes out the current buffer to the file you specify or to the output file associated with the buffer. Related CommandsDELETE BUFFER
Appendix A
|
Qualifier | OpenVMS Default |
---|---|
Command file | /COMMAND=TPU$COMMAND.TPU |
File creation | /CREATE |
Debugging package | /NODEBUG |
Specifying display mode | /DISPLAY=CHARACTER_CELL |
Initialization file | /INITIALIZATION=EVE$INIT.EVE |
Journaling | /JOURNAL |
Modifying main buffer | /MODIFY |
Specifying output | /OUTPUT=output-file |
Read-only access | /NOREAD_ONLY |
Recovery | /NORECOVER |
Section files | /SECTION=TPU$SECTION |
Start position | /START_POSITION=(1,1) |
Work file |
/WORK=SYS$SCRATCH:
TPU$WORK.TPU$WORK |
Using the character cell screen updater, the default insert or
overstrike mode is determined by your terminal setting.
A.1 Command File
Command file qualifiers determine the command file that DECTPU compiles and executes. Command files contain procedures and statements to extend or modify the editor. For example, you can use a command file to create additional EVE commands, define keys, or set attributes. You can also use a command file to set up a special text-processing environment for creating your own DECTPU application or for batch editing.
You cannot use wildcards to specify the command file. You can specify only one command file at a time.
If the command file you specify is not found, the editing session is aborted, returning you to the system prompt. If you do not explicitly specify a file, DECTPU looks for a command procedure but does not exit if no command procedure is found.
At startup, DECTPU compiles and executes a command file after loading a section file (if any) and before EVE executes an initialization file (if any). Thus, procedures, settings, and key definitions in a command file override those in the section file.
Use the following syntax for the command qualifiers:
$ EDIT/TPU /COMMAND[=command-file] (default) $ EDIT/TPU /NOCOMMAND |
There are three ways to specify the command file you want to use:
$ DEFINE TPU$COMMAND SYS$LOGIN:MYPROCS $ EDIT/TPU |
$ EDIT/TPU /COMMAND=MYPROCS |
For more information about DECTPU command files, see the DEC Text
Processing Utility Reference Manual.
A.2 File Creation
File creation qualifiers determine whether DECTPU creates a buffer when it does not find the input file. The processing results of using these qualifiers depends on the DECTPU application you are using.
In EVE, files are created by default. If the input file does not exist, EVE uses the input file name and file type to create the buffer name. If you do not specify an input file, EVE creates a buffer named MAIN.
Use the following syntax for the file creation qualifiers:
$ EDIT/TPU /CREATE (default) $ EDIT/TPU /NOCREATE |
Use the /NOCREATE qualifier to avoid invoking the editor in case you mistype the input file specification or to edit an existing file.
If EVE does not find an input file you have specified, it terminates the editing session and returns you to the system level, as in the following example:
$ EDIT/TPU NEW.DAT /NOCREATE Input file does not exist: NEW.DAT; |
Debug qualifiers determine whether DECTPU runs a debug file. A debug file is useful to test procedures for an application you are creating. DECTPU compiles and executes the debug file before executing TPU$INIT_PROCEDURE.
To start editing the code in the file you are debugging, use the GO command. You cannot use wildcards to specify the debug file. Use only one debug file at a time.
The debugger that is supplied with DECTPU is in SYS$SHARE:TPU$DEBUG.TPU. This file provides commands to manipulate variables and to control program execution.
Use the following syntax for the debug qualifier:
$ EDIT/TPU /DEBUG[=debug-file] $ EDIT/TPU /NODEBUG (default) |
There are two ways to specify a debug file of your own:
$ EDIT/TPU MYPROCS.TPU /DEBUG=MYDEBUG |
For more information about the debugger, refer to the source file or
see the DEC Text Processing Utility Reference Manual.
A.4 Specifying Display Mode
You can specify a display mode by using following syntax:
$ EDIT/TPU /DISPLAY={MOTIF, CHARACTER_CELL (default), DECWINDOWS} $ EDIT/TPU /INTERFACE={MOTIF, CHARACTER_CELL (default) , DECWINDOWS} $ EDIT/TPU /NODISPLAY $ EDIT/TPU /NOINTERFACE |
If you use /DISPLAY=DECWINDOWS and DECwindows is available, DECTPU displays the editing session in a separate window on your workstation screen and enables DECwindows features; for example, the EVE screen layout includes a menu bar and scroll bars. If DECwindows is not available, DECTPU works as if on a character-cell terminal.
Typically you turn off the display for batch jobs or when you are using an unsupported terminal. For batch jobs, use a DECTPU command file or EVE initialization file. For example, the following command uses a command file named BATCH.TPU to invoke DECTPU for batch editing:
$ EDIT/TPU /NODISPLAY /COMMAND=BATCH |
This startup file contains commands you want EVE to perform in batch
and should end with EXIT or QUIT. Some EVE commands cannot be used in
batch because they prompt for a keypress or other interactive response.
A.5 Initialization File
Initialization file qualifiers determine whether an application executes an initialization file. Processing methods with these qualifiers depend on the DECTPU application you are using. EVE initialization files contain commands to set attributes or define keys that you do not otherwise save in a section file. You cannot use wildcards to specify the initialization file. You can specify one initialization file at a time.
Settings and key definitions in an initialization file override those in a section file or in command file. When you invoke EVE, commands in an initialization file for buffer attributes, such as margins and tab stops, apply to all buffers specified on the command line and to an EVE system buffer named $DEFAULTS$. Buffers created during the session will have the same settings as $DEFAULTS$.
You can also execute an initialization file during an EVE session by using the @ command. This is useful when you want to set or change attributes or define keys for particular kinds of editing or to execute a series of related commands. EVE can create a buffer other than MAIN at startup.
Use the following syntax for the initialization qualifiers:
$ EDIT/TPU /INITIALIZATION[=init-file] (default) $ EDIT/TPU /NOINITIALIZATION |
There are three ways to specify the EVE initialization file you want to use:
$ DEFINE EVE$INIT SYS$LOGIN:MYINIT $ EDIT/TPU |
$ EDIT/TPU /INITIALIZATION=MYINIT |
Use /NOINITIALIZATION if you have defined the logical name EVE$INIT or
created an EVE$INIT.EVE file and do not want the initialization file
executed for a particular editing session. Also, using
/NOINITIALIZATION makes startup faster because EVE does not search for
an EVE$INIT.EVE file and does not parse commands at startup.
A.6 Journaling
Journaling qualifiers determine the type of journaling, if any. Journal files record your edits so that if a system failure interrupts your editing session, you can recover your work. Processing results with journaling qualifiers depends on the DECTPU application you are using.
There are two types of journaling, as follows:
$ EDIT/TPU /JOURNAL=MYSESSION |
For information about recovering your edits, see Section A.11.
Previous | Next | Contents | Index |