Document revision date: 30 March 2001

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.)

You can save attributes during your editing session by using the SAVE ATTRIBUTES or SAVE EXTENDED EVE command or as part of exiting or quitting. By default, if you have changed attributes and not saved them, then on exiting EVE prompts you as follows:

Command: SET CURSOR BOUND Command: SET FIND CASE EXACT Command: SET TABS VISIBLE . . . Command: EXIT Attributes were changed. Save them? [YES]

If you want to save the changes, press the Return key. EVE then does a SAVE ATTRIBUTES command before going on with the exit. If you do not want to save the changes, type NO and press Return. EVE then continues exiting.

To disable this prompting---typically, to make exiting faster or simpler---use the SET NOEXIT ATTRIBUTE CHECK command. However, the command does not apply to the current editing session because exit checking is itself a global setting and can be saved in a section file or command file. After you save it, the setting applies to future editing sessions in which you use the relevant section file or command file.

B.2 Saving Attributes in a Section File

Typically, you save attributes in a section file. A section file is in binary form and saves attributes, key definitions (including learn sequences), menu definitions, compiled procedures, and other extensions to the editor---including any saved in the section file you are using. In effect, the section file is your customized version of EVE. Because the section file is binary, it is executed quickly at startup.

To create a section file, you can use the SAVE EXTENDED EVE command (as in previous versions of EVE) or the SAVE ATTRIBUTES command. When using SAVE EXTENDED EVE, you can specify the section file on the command line or let EVE prompt you for the section file name. When using SAVE ATTRIBUTES, you specify the section file as a response to a prompt.

For example, the following command saves attributes and other customizations in a section file called MYSEC.TPU$SECTION in your current directory:

Command: SAVE ATTRIBUTES Save attributes in a section file [YES]? Return File to save in: MYSEC DISK$1:[USER]MYSEC.TPU$SECTION;1 created

To speed up saving in a section file, you can set a default section file---that is, the section file you want to save in without having to specify the file each time you save attributes---and you can disable section file prompting. Table B-5 shows you the interaction of the settings for default section file and section file prompting.

Table B-5 EVE Settings for Saving Attributes

Commands (Settings)	Effects with SAVE ATTRIBUTES
SET DEFAULT SECTION FILE SET SECTION FILE PROMPTING	When you save attributes, EVE asks you whether to save in a section file. If you respond YES (the default response), EVE saves in your default section file. If you respond NO, EVE asks whether to save in a command file.
SET DEFAULT SECTION FILE SET NOSECTION FILE PROMPTNG	When you save attributes, EVE saves in your default section file without prompting.
SET NODEFAULT SECTION FILE SET SECTION FILE PROMPTING	When you save attributes, EVE asks whether to save in a section file. If you respond YES, EVE asks for the name of a section file. If you respond NO, EVE asks whether to save in a command file. (Default settings.)
SET NODEFAULT SECTION FILE SET NOSECTION FILE PROMPTNG	When you save attributes, EVE asks whether to save in a command file. (See Section B.3.)

Typically, when you use SET DEFAULT SECTION FILE, you specify the section file you are going to use at startup for future editing sessions. The command does not determine the section file to be executed when you invoke the editor, but only the section file in which you save attributes and other customizations. For more information on how to specify the section file you want, see Section A.12.

Section files may be quite large, depending on the number of key definitions, menu definitions, and procedures you save. If you have limited disk space, you should save in a command file, which requires less disk space. For more information about creating and using section files, see Section A.12 or read the EVE online help topic on Section Files.

B.3 Saving Attributes in a Command File

A command file contains DECTPU procedures and statements that are compiled and executed at startup. In effect, this is a series of programs for extending EVE. (You can also use a command file for batch editing.) A command file may be slower at startup than a section file (depending on the number of procedures to be compiled and statements to be executed), but it takes up less disk space than a section file, and you can edit and print a command file. Also, if you edit your command file, you can recompile procedures during your editing session by using EXTEND commands. The default file type for command files is .TPU.

When you use the SAVE ATTRIBUTES command or when you save attributes on exiting or quitting, you can have EVE create or update a command file. EVE then generates a specially marked block of DECTPU statements for your settings and menu definitions. Thus, if you create a command file with procedures and key definitions of your own, you can have EVE append the block of attribute settings to this command file. Example B-1 is a sample of EVE-generated code.

Example B-1 EVE-Generated Code for Saving Attributes in a Command File

! EVE-generated code begin ! EVE attributes begin eve$set_find_case_sensitivity (FALSE); eve_set_box_noselect; eve_set_box_pad; eve_set_cursor_bound; eve_set_nodefault_command_file; eve_set_nodefault_section_file; eve_set_exit_attribute_check; eve_set_pending_delete; eve_set_nosection_file_prompting; eve_set_tabs ('INSERT'); eve_set_tabs ('VISIBLE'); ! EVE attributes end ! EVE-generated code end

To save attributes in a command file, use the SAVE ATTRIBUTES command, as follows:

Command: SAVE ATTRIBUTES Save attributes in a section file [YES]? NO Save attributes in a command file [YES]? [Return] Enter file name [TPU$COMMAND.TPU] MYCOM 14 lines written to file DISK$1:[USER]MYCOM.TPU;1

The prompt for the command file name shows, in brackets, the default command file that EVE uses if you simply press the Return key at the prompt without typing a file name. This default is one of the following:

• The command file specified with the /COMMAND qualifier when you invoked EVE
• A file called TPU$COMMAND.TPU in your current directory
• The command file defined by the logical name TPU$COMMAND

You can set your preferred default command file---that is, the command file you want EVE to create or update without having to specify the file each time you save attributes. For example, the following command sets your default command file as MYCOM in your current directory:

Command: SET DEFAULT COMMAND FILE MYCOM

If you want to save in a command file rather than in a section file, you should also use the SET NOSECTION FILE PROMPTING command. Then, when you save attributes, EVE asks whether to save in a command file without first asking whether to save in a section file.

Typically, when you use SET DEFAULT COMMAND FILE, you specify the command file you are going to use at startup for future editing sessions. The command does not determine the command file to be executed when you invoke EVE, but only the command file in which you save attributes and menu definitions.

For more information about creating and using command files, see Section A.1 or read the EVE online help topic on Command Files.

	privacy and legal statement
6021PRO_018.HTML