Document revision date: 19 July 1999

If you use buffer-change journaling (which is the EVE default) you recover one buffer at a time and can recover buffers from different editing sessions. For example, the following command invokes EVE to recover the text of a file named JABBER.TXT:

$ EDIT/TPU JABBER.TXT /RECOVER

This is the same as invoking EVE and using the RECOVER BUFFER command, as follows:

Command: RECOVER BUFFER JABBER.TXT

Recovery with a buffer-change journal file restores only your text; it does not restore settings, key definitions, and other customizations and it does not restore the contents of the INSERT HERE buffer or other system buffers. The recovery is usually quite fast.

A.11.2 Recovering with Keystroke Journaling

If you use keystroke journaling, you recover your editing session by reissuing the command for the original, aborted editing session, including all qualifiers, and adding the /RECOVER qualifier.

For example, the following command uses a keystroke journal file named MYSESSION to recover your edits:

$ EDIT/TPU/JOURNAL=MYSESSION . . . *** system failure *** $ EDIT/TPU /JOURNAL=MYSESSION /RECOVER

EVE then recovers your editing session stroke-by-stroke. After the recovery, exit from the file if you want to save the recovered text.

A.11.3 Keystroke Journaling Restrictions

Keystroke journaling does not work on DECwindows and has the following restrictions regarding recovery. These restrictions do not apply to buffer-change journaling. Because of these restrictions, DIGITAL recommends the use of buffer-change journaling.

• To recover your edits with a keystroke journal file, all relevant files must be in the same state as at the start of the session being recovered---including any files you wrote out (saved) before the system failure. Therefore, before doing the recovery, you may want to rename the saved files or move them to a different directory to ensure that the recovery uses the original versions of the files.
• Check that the same section file, command file, and initialization file are used as those in the original editing session, and that the recovery will use the correct versions of these files. For example, if you created a new version of your section file before the system failure, you must use the original version of your section file to recover the editing session.
• Check that the following terminal settings are the same as when you began the original editing session because they may affect how your keystrokes are replayed:
  • Device_Type
  • Edit_mode
  • Eightbit
  • Page
  • Width
• Recovery with a keystroke journal file may fail or may not work properly if you used Ctrl/C during the original editing session. Ctrl/C is not recorded in the keystroke journal file. Therefore, when you recover your edits, an operation that was canceled with Ctrl/C is replayed without interruption.
• If you keep an EVE editing session active in one process and use the ATTACH or SPAWN built-ins to move to another process, the keystroke journal file records SPAWN and ATTACH commands in EVE but does not record operations done in the other process. If these other operations affected any files used in the original editing session---for example, if you spawned a subprocess from EVE and then purged, renamed, or deleted any files---the recovery may fail or may not work properly.
• If you used the EVE command DCL or SHELL, the recovery may fail or may not work properly, particularly if you edited the DCL buffer. For example, if you cut a file name from a directory list in the DCL SHELL buffer and pasted it into an EVE command line, the keystroke recovery replays the operations, but the directory list or the file name may not be the same as in the original session.

For more information about journaling and recovery, see DEC Text Processing Utility Reference Manual.

A.12 Section Files

You can specify the section file you want to use, if any. A section file contains, in binary form, key definitions, compiled procedures, global variables, and so on. Effectively, the section file is the DECTPU application you run---whether a customized version of EVE or some other application you have created.

A.12.1 Specifying a Section File

Use the following syntax for the section file qualifiers:

$ EDIT/TPU /SECTION[=section-file] $ EDIT/TPU /NOSECTION

The default section file is defined system-wide by the logical name TPU$SECTION. This specifies the standard EVE section file (EVE$SECTION.TPU$SECTION).

There are two ways to specify the section file you want to use:

• Define the logical name TPU$SECTION to specify your section file. This is useful if you want to run that section file for all or most sessions. Your definition of the logical name overrides the system-wide default. You can put the definition in your LOGIN.COM file. For example, the following commands define TPU$SECTION as MYSECT.TPU$SECTION in your top-level login directory and then use that section file instead of the standard EVE section file to invoke DECTPU:

  $ DEFINE TPU$SECTION SYS$LOGIN:MYSECT $ EDIT/TPU

• Use the /SECTION= qualifier and specify the section file. This overrides any definition of the TPU$SECTION logical name. For example, the following command uses a section file named MYSECT.TPU$SECTION in your top-level login directory instead of the standard EVE section file to invoke DECTPU:

  $ EDIT/TPU /SECTION=SYS$LOGIN:MYSECT

DECTPU assumes the section file is in SYS$SHARE. If your section file is stored elsewhere, use a complete file specification, including the device (disk) and directory. You cannot use wildcards to specify the section file. You use one section file at a time.

A.12.2 Specifying No Section File

If you use the /NOSECTION qualifier, DECTPU does not use any section file. This prevents even the default interface from being used. DECTPU is virtually unusable unless you specify a command file with procedures and executable statements that set up a text-processing environment. Use /NOSECTION when you create your own application without using EVE as a base or when you use /NODISPLAY for batch editing. For example, the following command uses a command file named USER_APPL.TPU to invoke DECTPU without a section file:

$ EDIT/TPU /NOSECTION /COMMAND=USER_APPL

At startup, a section file, if one is being used, is loaded first---that is, before DECTPU executes a command file (if any) and before EVE executes an initialization file (if any). Thus, your procedures, settings, and key definitions in a command file or initialization file override those in the section file.

A.12.3 Creating a Section File

To create a section file, do either of the following:

• In EVE, use the SAVE EXTENDED EVE command. For example, the following command creates a section file named MYSEC.TPU$SECTION in your current directory:

  Command: SAVE EXTENDED EVE MYSEC

• In a DECTPU command file, use the SAVE built-in procedure, usually at the end of the command file. For example, the following statement creates a section file named MYSEC.TPU$SECTION in your top-level login directory:

  . . . SAVE ("SYS$LOGIN:MYSEC"); ! create the section file EXIT; ! done -- end of command file

A section file is cumulative; it saves the current key definitions and other customizations---and those already in the section file you are using. In EVE, the section file saves the following:

• Compiled procedures
• Global settings (attributes)
• Key definitions and LEARN sequences
• Menu definitions for the DECwindows interface

For more information about creating section files, see the DEC Text Processing Utility Reference Manual.

A.13 Start Position

Start position qualifiers determine the row and column where the cursor first appears in the buffer that you specify on the command line.

For EVE, the default start position is 1,1 (row 1, column 1), which is the upper left corner of the buffer. Use of start position qualifiers do not affect the initial cursor position when you create another buffer during the editing session and does not limit the buffer size.

Use the following syntax for the start position qualifier:

$ EDIT/TPU /START_POSITION=(row[,column])

Use the start position qualifier to begin editing at a particular line (or row) or at a particular character position (or column). For example, when you want to skip over a standard heading in a file or if a batch log file or error message tells you there is an error on a given line of a program, you can specify that line number as the starting row. Then when you edit the program source file, the cursor moves directly to that line. The following command edits a file named TEST.COM and puts the cursor on line 10, column 5:

$ EDIT/TPU TEST.COM /START_POSITION=(10,5)

If you just want to start at a particular line in a file, you can omit the second parameter (the column).

A.14 Work File

Work file qualifiers determine the work file that is used to swap memory for editing very large files. There is one work file per editing session. The work file is a temporary file that is automatically deleted when you exit.

Use the following syntax for the work file qualifiers:

$ EDIT/TPU /WORK[=work-file] $ EDIT/TPU /NOWORK

The default work file is named TPU$WORK.TPU$WORK. DECTPU creates the work file in SYS$SCRATCH unless you specify otherwise. There are two ways to specify a different work file:

• Define the logical name TPU$WORK. This is useful if you want the work file to be created in an area other than SYS$SCRATCH, such as on a larger disk. You can put the definition in your LOGIN.COM file.
• Use the /WORK= qualifier and specify the work file. This overrides any definition of the TPU$WORK logical name. For example, the following command invokes DECTPU and specifies the work file to be SYS$SCRATCH:MYWORK.TPU$WORK:

  $ EDIT/TPU /WORK=MYWORK

Table B-1 lists the EVE default settings---the settings EVE uses unless you specify otherwise. You may want to refer to this table to check which settings you want to change when creating an initialization file. Some settings are global (applying for all buffers you edit); others are buffer specific. For example, the type of cursor motion (bound or free) and tab mode (insert, spaces, or movement) are the same for all buffers you edit; margins, paragraph indent, and tab stops can be set differently for each buffer.

Table B-1 EVE Default Global Settings for All Buffers

Default Setting	Effects
SET BOX NOSELECT	Disables box-style selection, cutting, and pasting so you can select and edit standard linear ranges.
SET BOX PAD	Enables padding and overstriking for box editing, regardless of the mode of the buffer.
SET CURSOR FREE	You can move the cursor anywhere in the buffer and enter text there, as opposed to a bound cursor, which cannot move into the unused portion of the buffer. Using SET KEYPAD WPS automatically enables a bound cursor.
SET EXIT ATTRIBUTE CHECK	If you changed attributes, then when you exit or quit, EVE asks whether you want to save them.
SET FIND CASE NOEXACT	EVE finds any occurrence of a text string if you enter the search string in all lowercase.
SET FIND NOWHITESPACE	FIND and WILDCARD FIND commands match spaces and tabs in the search string exactly as entered and do not search across a line break.
SET FUNCTION KEYS NODECWINDOWS	Keeps the normal key definitions (EVE default, EDT keypad, or WPS keypad) rather than defining some keys for DECwindows functions.
SET KEYPAD NUMERIC or SET KEYPAD VT100	On VT400-series, VT300-series, and VT200-series terminals, keys on the numeric keypad are undefined, except for the PF4 and Enter keys. On VT100-series terminals, the numeric keypad is used for the EVE default key bindings. Control keys are defined the same on either type of terminal. Also, you can set the EDT keypad or WPS keypad on either type of terminal.
SET NOCLIPBOARD	Copy, cut, and paste operations use the INSERT HERE buffer in EVE. On DECwindows, you can enable the clipboard, which lets you transfer text between EVE and other DECwindows applications. WPS keypad keys do not use the clipboard, regardless of the setting.
SET NODEFAULT COMMAND FILE	EVE uses one of the following as the default command file for saving attributes: Command file specified with the /COMMAND= qualifier when you invoked EVE Command file named TPU$COMMAND.TPU in the current directory A command file defined by the logical name TPU$COMMAND
SET NODEFAULT SECTION FILE	If section file prompting is enabled (the default), EVE prompts whether to save attributes in a section file. If section file prompting is disabled, EVE prompts whether to save attributes in a command file.
SET NOGOLD KEY	EVE does not have a default GOLD key. Setting the EDT or WPS keypad makes PF1 the GOLD key, overriding any current definition of PF1, unless you set a different key as GOLD.
SET NOPENDING DELETE	Using DELETE or typing new text does not erase a selection.
SET SCROLL MARGINS 0 0	Scrolling begins automatically when you move past the top or bottom of the window.
SET SECTION FILE PROMPTING	When you save attributes and other customizations, EVE prompts for a section file.
SET TABS INSERT	Using TAB inserts a tab character. You can set the tab mode to insert spaces instead of a tab character, or to move the cursor without inserting anything.
SET TABS INVISIBLE	Tab characters appear during editing as blank spaces, as opposed to visible tabs, which appear as a small HT (horizontal tab).
SET WIDTH 80	The width of the EVE screen layout is the same as your terminal setting---typically 80 columns.
SET WILDCARDS VMS	The WILDCARD FIND command uses OpenVMS-style wildcards, such as the asterisk (*) to match any amount of text on a line, the percent sign (%) to match a single character on a line, and so on.

Table B-2 lists the EVE default settings for buffer-specific settings.

Table B-2 EVE Default Buffer-Specific Settings

Default Setting	Effects
FORWARD	Commands like FIND and MOVE BY LINE move the cursor to the right and down. You can change the direction to reverse (left and up).
INSERT MODE	Characters you type are inserted at the current position, pushing existing text to the right and down. You can change the mode to overstrike.
SET BUFFER MODIFIABLE	Buffers you create can be modified (edited). You can set the buffer to unmodifiable.
SET BUFFER WRITE	On exiting, EVE writes out (saves) your buffers if you have made any changes. You can set the buffer to read-only.
SET JOURNALING ALL	Buffer-change journaling is enabled for all your text buffers.
SET LEFT MARGIN 1	This is the leftmost column. When you press the Return key or use FILL commands or when EVE wraps text, new lines start at the left margin of the buffer.
SET PARAGRAPH INDENT 0	Paragraphs you create or ones you reformat with FILL commands start at the current left margin of the buffer---with no indent.
SET RIGHT MARGIN 79	The default right margin is one column less than the width set for your terminal. If the width is 80 columns, the default right margin is 79. When you use FILL commands or when you type at the end of a line, EVE wraps text at the right margin of the buffer.
SET TABS EVERY 8	Tab stops are set at columns 9, 17, 25, 33, 41, and so on. You can set tab stops at different intervals.
SET WRAP	As you type text at the end of a line, EVE wraps text at the right margin of the buffer, without your having to press the Return key or use FILL commands.

You can save some EVE settings or attributes in a section file or as EVE-generated code in a DECTPU command file. You can set other attributes, such as margins and tab stops, in an initialization file.

The following is a sample EVE initialization file that contains commands to set editing preferences and to define keys:

! MYINIT.EVE initialization file ! SET LEFT MARGIN 5 SET PARAGRAPH INDENT 4 SET RIGHT MARGIN 70 SET TABS EVERY 10 SET SCROLL MARGINS 9% 9% SET FIND WHITESPACE ! Key definitions SET KEYPAD EDT DEFINE KEY= F20 SHOW BUFFERS DEFINE KEY= Ctrl/P PAGINATE DEFINE KEY= GOLD-G GET FILE DEFINE KEY= KP7 WPS GOLD-R

When you use an initialization file to invoke EVE, commands in the initialization file for margins, tabs stops, and other buffer-specific settings apply to the MAIN (or first) buffer and to an EVE system buffer called $DEFAULTS$. The $DEFAULTS$ buffer is a template buffer: when you create a buffer---for example, by using the GET FILE command---EVE uses the settings of the $DEFAULTS$ buffer so that each new buffer has the same settings. Thus, if your initialization file contains the command SET RIGHT MARGIN 70, each buffer you create will have that right margin.

To find out the default settings, use the SHOW DEFAULTS BUFFER command. To find out the settings of the buffer you are editing, use the SHOW command.

B.1 Saving Attributes

Attributes are global settings, some of which you can save in a section file or DECTPU command file for future editing sessions. Table B-3 shows the settings that you can save.

Table B-3 EVE Commands for Setting Attributes

Command	Default Setting
SET BOX [NO]PAD	SET BOX PAD
SET BOX [NO]SELECT	SET BOX NOSELECT
SET [NO]CLIPBOARD	SET NOCLIPBOARD
SET CURSOR BOUND FREE	SET CURSOR FREE
SET [NO]DEFAULT COMMAND FILE	SET NODEFAULT COMMAND FILE
SET [NO]DEFAULT SECTION FILE	SET NODEFAULT SECTION FILE
SET [NO]EXIT ATTRIBUTE CHECK	SET EXIT ATTRIBUTE CHECK
SET FIND CASE [NO]EXACT	SET FIND CASE NOEXACT
SET [NO]PENDING DELETE	SET NOPENDING DELETE
SET [NO]SECTION FILE PROMPTING	SET SECTION FILE PROMPTING
SET TABS INSERT MOVEMENT SPACES	SET TABS INSERT
SET TABS [IN]VISIBLE	SET TABS INVISIBLE

If you have an EVE initialization file that contains commands for these settings, you can delete those command lines after you save the settings in your section file or command file.

Other global settings (such as scroll margins or the type of wildcards) and any buffer settings (such as margins or tab stops) are not saved. Typically, you use an initialization file for those settings.

Table B-4 summarizes the new and changed commands for saving attributes.

Table B-4 EVE Commands for Saving Attributes

Command	Usage or Effects
SAVE ATTRIBUTES	Saves attributes in a section file or command file, depending on your responses to EVE prompts or settings done with other EVE commands. If you save in a section file, the effect is the same as SAVE EXTENDED EVE. If you save in a command file, EVE generates a specially marked block of DECTPU statements for attribute settings and menu definitions, and either creates a command file or updates an existing command file with this block of statements.
SAVE EXTENDED EVE	Creates a section file, saving attributes, key definitions, menu definitions, compiled procedures, and other extensions, such as global variables set with a DECTPU statement. If you do not specify a section file on the command line, EVE prompts you for one or uses your default section file (if you set a default).
SAVE SYSTEM ATTRIBUTES	Saves EVE default attributes in a section file or command file. This is useful if you want to restore your section file or command file to the standard EVE settings and menu definitions. See Section B.4.
SET BOX NOPAD	Disables padding and overstriking for box editing, unless the mode of the buffer is overstrike.
SET BOX NOSELECT	Disables box-style selection, cutting, and pasting. (Default setting.)
SET BOX PAD	Enables padding and overstriking for box editing, regardless of the mode of the buffer. (Default setting.)
SET BOX SELECT	Enables box selection, cutting, and pasting.
SET DEFAULT COMMAND FILE	Determines the command file for saving attributes. Does not determine the command file to be executed at startup, if any.
SET DEFAULT SECTION FILE	Determines the section file for saving attributes. Does not determine the section file to be executed at startup.
SET EXIT ATTRIBUTE CHECK	If you changed attributes, then when you exit or quit, EVE asks if you want to save your changes. (Default setting.)
SET NODEFAULT COMMAND FILE	When you save attributes, the default command file is TPU$COMMAND.TPU in your current directory or the command file that was executed at startup. See Section B.3. (Default setting.)
SET NODEFAULT SECTION FILE	When you save attributes, EVE asks for the name of the section file you want to create (unless you disabled section file prompting). (Default setting.)
SET NOEXIT ATTRIBUTE CHECK	Disables attribute checking, typically to speed up or simplify exiting or quitting. Does not apply to the editing session in which you issue the command. Applies only to the editing sessions in which you use the section file or command file in which you saved the setting.
SET NOSECTION FILE PROMPTING	Disables prompting for a section file when you save attributes, typically to speed up or simplify saving attributes in a default section file or in a command file.
SET SECTION FILE PROMPTING	When you save attributes, EVE prompts you for the name of a section file. (Default setting.)

	privacy and legal statement
6021PRO_017.HTML