![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
You can customize section files and command files interactively from the EVE editor. You create initialization files separately.
When saving your customizations in a section file or command file, use the SAVE ATTRIBUTES command or the SAVE EXTENDED EVE command when you exit from or quit the editor.
This list summarizes the commands for saving attributes:
If you have changed attributes and not saved them, EVE asks if you want to save the changed attributes when you exit from
The following example shows how you can save attributes when you exit from EVE:
Command: SET CURSOR BOUND
Command: MOVING_TEXT
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 breaka SAVE ATTRIBUTES command before exiting. If you do not want to save the changes, type No and press Return. EVE then continues exiting.
To disable this prompting, for a faster or simpler exit, 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.
Other global attributes (such as scroll margins or the types of wildcards) and any buffer-specific attributes (such as margins or tab stops) are not saved in a section file or a command file. Typically, you use an initialization file for those settings.
There are several ways in which you can use all your customizations in future editing sessions. You can combine different types of startup files in the following ways:
This section lists the categories of commands for EVE attributes and features and shows in what type of startup file you can save them. By placing your definitions and procedures in a startup file, you can invoke the editor and automatically establish the editing environment your task requires.
The following table lists key definitions and what type of files they can be used in:
| Key Definitions | Section | Command | Initialization |
|---|---|---|---|
| DEFINE KEY | X | X | X |
| LEARN | X | -- | -- |
| SET FUNC KEYS [NO]DECWINDOWS | X | X | X |
| SET [NO]GOLD KEY | X | X | X |
| SET KEYPAD [NO]EDT | X | X | X |
| SET KEYPAD [NO]WPS | X | X | X |
| SET KEYPAD VT100 | X | X | X |
| SET KEYPAD NUMERIC | X | X | X |
| UNDEFINE KEY | X | X | X |
The following table lists global settings-1 and what type of files they can be used in:
| Global Settings-1 | Section | Command | Initialization |
|---|---|---|---|
| SET BOX [NO]PAD | X | X | X |
| SET BOX [NO]SELECT | X | X | X |
| SET CURSOR FREE or BOUND | X | X | X |
| SET [NO]CLIPBOARD | X | X | X |
| SET [NO]DEFAULT COMMAND FILE | X | X | X |
| SET [NO]DEFAULT SECTION FILE | X | X | X |
| SET [NO]EXIT ATTRIBUTE CHECK | X | X | X |
| SET FIND CASE [NO]EXACT | X | X | X |
| SET [NO]PENDING DELETE | X | X | X |
| SET [NO]SECTION FILE PROMPTING | X | X | X |
| SET TABS INSERT, MOVEMENT, or SPACES | X | X | X |
| SET TABS [IN]VISIBLE | X | X | X |
The following table lists global settings-2 and what type of files they can be used in:
| Global Settings-2 | Section | Command | Initialization |
|---|---|---|---|
| SET FIND [NO]WHITESPACE | -- | -- | X |
| SET SCROLL MARGINS | -- | -- | X |
| SET WIDTH | -- | -- | X |
| SET WILDCARDS VMS or ULTRIX | -- | -- | X |
The following table lists buffer settings and what type of files they can be used in:
| Buffer Settings | Section | Command | Initialization |
|---|---|---|---|
| FORWARD or REVERSE | -- | -- | X |
| INSERT MODE or OVERSTRIKE MODE | -- | -- | X |
| SET BUFFER | -- | -- | X |
| SET [NO]JOURNALING ALL | -- | -- | X |
| SET LEFT MARGIN | -- | -- | X |
| SET PARAGRAPH INDENT | -- | -- | X |
| SET RIGHT MARGIN | -- | -- | X |
| SET TABS AT or EVERY | -- | -- | X |
| SET [NO]WRAP | -- | -- | X |
DECTPU procedures can be used in section and command files but not initialization files.
To save a section file, use the SAVE EXTENDED EVE command or the SAVE ATTRIBUTES command. Using SAVE EXTENDED EVE, you can specify the section file on the command line or let EVE prompt you for the section file name. 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---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.
The command shown in this example saves attributes and other customized settings in a section file entitled 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:
| Command Settings | Effect with SAVE ATTRIBUTES |
|---|---|
|
SET DEFAULT SECTION FILE
SET SECTION FILE PROMPTING |
When you save attributes, EVE ask 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 |
Default settings. 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. |
|
SET NODEFAULT SECTION FILE
SET NOSECTION FILE PROMPTING |
When you save attributes, EVE asks whether to save in a command file. |
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 customized settings. To specify the section file you want executed at startup, do either of the following:
$ EDIT/TPU/SECTION=MYEVE
$ DEFINE TPU$SECTION SYS$LOGIN:MYEVE $ EDIT/TPU
In specifying the section file to be executed, you must use a complete file specification, including the device (or disk) and directory; otherwise, DECTPU assumes the section file is in SYS$SHARE.
Section files may be quite large, depending on the number of customized settings 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.
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. 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 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.TPU 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.
When you use SET DEFAULT COMMAND FILE, you usually 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. To specify the command file you want executed at startup, do any of the following:
$ EDIT/TPU/COMMAND=MYEVE
$ DEFINE TPU$COMMAND SYS$LOGIN:MYEVE $ EDIT/TPU
For more information about creating and using command files, see the EVE online help topic entitled Command Files.
If you are accustomed to the EDT editor, you can customize EVE to work in similar ways by using a section file, an initialization file, or both, or by using DECTPU procedures.
Typically, you save key definitions, learn sequences, and other extensions in a section file (created with the SAVE EXTENDED EVE command). Use an EVE initialization file to set editing preferences or private defaults, such as margins and tabs, which are not saved in the section file.
The SET KEYPAD EDT command defines several keys to emulate EDT. You can put the command in your EVE initialization file or save the keypad setting in a section file. Most keypad functions work as in EDT, although the names may differ. For more information, see the online help topic called EDT Differences.
Use DEFINE KEY commands to define keys that are not otherwise defined by SET KEYPAD EDT. Put the key-definition commands in your initialization file or save the definitions in a section file.
The following sets of EDT and EVE key definitions are equivalent:
In EDT:
DEF KEY GOLD 2 "EXT SHOW BUFFER." DEF KEY GOLD l "CHGLW." DEF KEY GOLD u "CHGUW." DEF KEY GOLD 10 "EXT FIND=?.." DEF KEY GOLD 9 "CUTSR PASTE." DEF KEY cont n "EXT QUIT." DEF KEY func 34 "SHL."
In EVE:
DEF KEY= GOLD E2 SHOW BUFFERS DEF KEY= GOLD l LOWERCASE WORD DEF KEY= GOLD U UPPERCASE WORD DEF KEY= GOLD PF2 BUFFER DEF KEY= GOLD KP9 STORE TEXT DEF KEY= Ctrl/N QUIT DEF KEY= F20 SHIFT RIGHT 8
Note the differences between EDT and EVE in some key names, as well as differences in command names. For more information about key names, see Section A.2.
Use the SET CURSOR BOUND command to enable an EDT style bound cursor. By default, EVE uses a free cursor, which you can move anywhere in the buffer. You can save the setting in your section file or DECTPU command file.
Put the SET RIGHT MARGIN command in your EVE initialization file to set a wrap limit for entering text and for FILL commands. For example, the following EDT and EVE commands are equivalent:
In EDT:
SET WRAP 70
In EVE:
SET RIGHT MARGIN 70
(The EVE command SET WRAP corresponds to the EDT command SET NOTRUNCATE.)
Put the SET SCROLL MARGINS command in your EVE initialization file to set distances for scrolling to begin automatically as you move the cursor up or down. For example, with a 24-line terminal screen (21-line main window), the following EDT and EVE commands are equivalent:
In EDT:
SET CURSOR 5:15
In EVE:
SET SCROLL MARGINS 5 6
EVE scroll margins are measured from the top and bottom, respectively. In EDT, both scroll margins are measured from the top. You can specify numbers of lines or percentages of the window size. Also, the size of the EVE main window depends on your terminal settings. For example, on a workstation, the EVE main window may be longer than 21 lines.
Searches follow EVE rules for case sensitivity. Put SET FIND commands in your EVE initialization file to set the way you want searches to work. For example, the following EDT and EVE commands are nearly equivalent:
In EDT:
SET SEARCH EXACT
In EVE:
SET FIND CASE EXACT
These commands are not exact equivalences because EVE always matches diacritical marks exactly as entered in the search string.
Use DECTPU procedures in place of EDT macros. Create a buffer that contains the procedures and then use EXTEND commands to compile the procedures with EXTEND commands. Or, put the procedures in a DECTPU command file and then use the /COMMAND qualifier to invoke EVE. In either case, you can save the compiled procedures in your section file.
You can also use the LEARN command to bind the corresponding EVE commands to a single key. You can then save the key definition in your section file. Another method is to put the corresponding EVE commands in an initialization file.
The following examples show a macro from an EDT startup file which is translated into a DECTPU procedure. Each macro creates a new command, WIDEN, which sets the display to 132 columns and sets the right margin to 120.
EDT Macro:
FIND =WIDEN INSERT;SET SCREEN 132 INSERT;SET WRAP 120 FIND =MAIN.
DECTPU Procedure:
PROCEDURE EVE_WIDEN; EVE_SET_WIDTH (132); EVE_SET_RIGHT_MARGIN (120); ENDPROCEDURE;
To execute the macro or procedure, use the following commands:
In EDT:
* DEFINE MACRO WIDEN * WIDEN
In EVE:
Command: EXTEND EVE WIDEN Command: WIDEN
You can usually convert EDT macros and key definitions that use nokeypad specifiers into DECTPU procedures or learn sequences. The following examples show an EDT key definition that uses nokeypad mode and the corresponding DECTPU procedure and key definition. In each case, you define Comma on the numeric keypad to transpose or swap the current and previous character. The --C in EDT nokeypad statements can be translated as MOVE_HORIZONTAL (--1) in DECTPU procedures.
In EDT:
DEFINE KEY 19 AS "-C D1C +C UNDC."
In DECTPU:
PROCEDURE USER_TRANSPOSE
LOCAL SWAP_THIS;
SWAP_THIS := ERASE_CHARACTER (1);
MOVE_HORIZONTAL (-1);
EVE$INSERT_TEXT (SWAP_THIS);
RETURN (TRUE);
ENDPROCEDURE;
EVE$DEFINE_KEY ("USER_TRANSPOSE", COMMA, , EVE$X_USER_KEYS);
Setting the EDT keypad does not define keys for EDT style tab adjustment. However, you can get similar effects by defining a key for the WPS keypad Ruler key (GOLD R) and then using the ruler to add or delete tab stops.
In this tutorial, the command defines F20 as the WPS Ruler key (without having to enable the WPS keypad):
Command: DEFINE KEY= F20 WPS GOLD-R
Then, to add or delete tab stops, follow these steps:
| Step | Task |
|---|---|
| 1 |
Press whatever key you have defined as the Ruler key.
EVE displays a ruler at the bottom of the current window (just above the status line for the window). The cursor appears in the ruler. Tab stops are marked with a T. |
| 2 |
Put the cursor where you want to add or delete a tab stop.
For example, press the left and right arrow keys to move to a particular column in the ruler or press the Tab key to move to the next tab stop ( T) in the ruler. |
| 3 | Type a T or t at that location to set the tab stop or, if there is already a tab there, to delete it. The new tab stops are immediately applied to the buffer you were editing. |
| 4 | Repeat steps 2 and 3 to add or delete other tab stops. |
| 5 | To exit from the ruler and resume editing, press the Return key or GOLD Return. |
This appendix describes the DEC Multinational character set and the DCL character set. It includes information about:
The DEC Multinational character set is an 8-bit character set with 256 characters; the first 128 characters in the set correspond to the ASCII character set. Each character has a value in the range 0 to 255 decimal.
Section B.2.3 represents the ASCII character set (characters with decimal values 0 through 127). The first half of each numbered column identifies the character as you would enter it on a VT-series terminal or workstation or as you would see it on a printer (except for the nonprintable characters). The remaining half of each column identifies the character by the binary value of the byte; the value is stated in three radixes---octal, decimal, and hexadecimal.
The uppercase letter A has, under ASCII conventions, a storage value of hexadecimal 41 (a bit configuration of 01000001), equivalent to 101 in octal notation and 65 in decimal notation. DCL uses hexadecimal values to perform string comparisons. (For a description of string comparisons, see Chapter 14.)
6489P040.HTM OSSG Documentation 22-NOV-1996 13:17:38.00
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.