![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
For example, the following command defines the PF1 key as the GOLD key:
SET GOLD KEY PF1
The LEARN command assigns a sequence of keystrokes, called a learn sequence, to a single key or control key sequence. With learn sequences, you can enter the same series of keystrokes in a buffer any number of times by pressing one key. All learn sequences are discarded when you terminate an EVE editing session unless you use the SAVE ATTRIBUTES command or the SAVE EXTENDED EVE command to save them from one editing session to the next.
To define a learn sequence, take these steps:
| Step | Task |
|---|---|
| 1 | Enter the LEARN command. |
| 2 |
Type the keystrokes to be remembered.
You can press keys already defined, type text, or both. |
| 3 | Press Ctrl/R. |
| 4 | At the prompt, press the key to be associated with the learn sequence, such as F17 or PF3. |
| 5 | To cancel the learn sequence, press the Return key or Ctrl/M. |
The message "Key sequence remembered" appears if you have successfully defined a key.
To define a learn sequence that inserts a string of text into your file when you press Ctrl/F, follow these steps:
| Step | Task |
|---|---|
| 1 |
Invoke EVE to edit the file RHYMES.DAT.
She rhymes with tree,
|
| 2 |
Move the cursor to the end of the buffer.
To begin the definition of the learn sequence, press the Do key, and enter the LEARN command. |
| 3 |
Insert the following text, which EVE is to remember, at the end of your
file:
And what is a rhyme?
|
| 4 | Press Ctrl/R. |
| 5 | Press Ctrl/F, the key to which you are assigning the learn sequence. |
For the rest of the editing session, when you press Ctrl/F, EVE inserts the text "And what is a rhyme?" wherever the cursor is positioned at the time.
You can save most global attributes in a section file or DECTPU command file for future editing sessions. You can also set a default section file or command file to be created or updated for saving attributes.
This list shows 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 to all buffers you edit), and 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, whereas you can set margins, paragraph indents, and tab stops differently for each buffer.
This list shows the EVE default settings for buffer-specific settings:
When editing EVE command lines---such as when you recall a command---the default direction is reversed and the cursor is bound. The default mode on a character-cell terminal matches your terminal setting.
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.
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.
When you use an initialization file to invoke EVE, commands in the initialization file for margins, tab stops, and other buffer-specific settings apply to the Main (or first) buffer and to an EVE system buffer named $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.
This 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
Attributes are global settings, some of which can be saved in a section file or DECTPU command file for future editing sessions. Table A-1 shows the settings that you can save:
| Command | Default Setting |
|---|---|
| SET BOX [NO]PAD | SET BOX PAD |
| SET BOX [NO]SELECT | SET BOX NOSELECT |
| SET [NO]CLIPBOARD | SET NOCLIPBOARD |
SET CURSOR
|
SET CURSOR FREE |
| SET [NO]DEFAULT COMMAND FILE | SET NODEFAULT COMMAND FILE |
| SET [NO]DEFAULT SECTION FILE | SET NODEFAULT SECTION FILE |
| SET FIND CASE [NO]EXACT | SET FIND CASE NOEXACT |
| SET [NO]EXIT ATTRIBUTE CHECK | SET EXIT ATTRIBUTE CHECK |
| SET [NO]SECTION FILE PROMPTING | SET SECTION FILE PROMPTING |
| SET [NO]PENDING DELETE | SET NOPENDING DELETE |
SET TABS
|
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 types of wildcards) and any buffer settings (such as margins or tab stops) are not saved. Typically, you use an initialization file for those settings.
The following list summarizes the new and changed commands for saving attributes:
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 executes a SAVE ATTRIBUTES command before continuing the exit. If you do not want to save the changes, type No and press the Return key. 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 that you can save 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.
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.
To speed up saving in a section file, you can set a default section file, which you can then save in without having to specify the file each time you save attributes. You can also disable section file prompting.
The command shown in this example saves attributes and other customizations in a section file called MYSEC.TPU$SECTION in the 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
The following table shows the interaction of the settings for default section file and section file prompting:
| Commands Settings | Effect 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 PROMPTING |
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 PROMPTING |
When you save attributes, EVE asks whether to save in a command file (see Section A.4.16). |
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.
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 the EVE online help topic called Section Files.
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. In addition, a command file can be edited and printed. 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 created 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 A-1 is an example of EVE-generated code for saving attributes in a command file.
Example A-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 press the Return key at the prompt without typing a file name. This default is one of the following:
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 the EVE online help topic called Command Files.
The SAVE SYSTEM ATTRIBUTES saves EVE default settings and menu entries in a section file or command file. Thus, if you set several attributes and defined or undefined menu entries, you can use SAVE SYSTEM ATTRIBUTES to restore the standard EVE settings and menus to your section file or command file.
SAVE SYSTEM ATTRIBUTES does not change the settings currently in effect---for example, it does not enable free cursor motion or invisible tabs---but saves only the EVE defaults in a section file or command file.
You can use DECTPU within EVE to create DECTPU command files and to use the DECTPU debugging package.
File creation switches and qualifiers determine whether DECTPU creates a buffer when it does not find the input file. The processing results of using this qualifier depend 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.
To create DECTPU command files, use the /CREATE or /NOCREATE qualifiers, as follows:
$ 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 only 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 switches and qualifiers determine whether DECTPU runs a debug file. A debug file is useful for testing procedures for an application that you are creating.
To edit the code in the file you are debugging, follow these rules:
6489P038.HTM OSSG Documentation 22-NOV-1996 13:17:34.49
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.