![[Compaq]](../images/compaq.gif)
![[Go to the documentation home page]](../images/buttons/bn_site_home.gif)
![[How to order documentation]](../images/buttons/bn_order_docs.gif)
![[Help on this site]](../images/buttons/bn_site_help.gif)
![[How to contact us]](../images/buttons/bn_comments.gif)
![[OpenVMS documentation]](../images/ovmsdoc_sec_head.gif)
| Document revision date: 30 March 2001 | |
|
|
|
|
|
|
| Previous | Contents | Index |
SET DEFAULT SECTION FILE section-file
section-file
The name of the section file you want EVE to use by default. The default file type is .TPU$SECTION. If you use SET DEFAULT SECTION FILE and do not specify a file name on the command line, EVE prompts you. The prompt shows the name of the current, default section file, if one is set. If you have not already set a default section file, the prompt shows SYS$LOGIN:EVE$SECTION.TPU$SECTION.
The SET DEFAULT SECTION FILE command determines the section file that EVE creates to save attributes, key definitions, and other customizations. You do not need to specify the section file each time you invoke EVE. SET DEFAULT SECTION FILE does not determine the section file loaded at startup. Instead, it determines only the section file created for saving attributes and menu entries.For more information about using section files, read the online help topic called Section Files.
The following table shows the effects of SET DEFAULT SECTION FILE, depending on whether you save attributes by enabling or disabling section file prompting:
Prompt Settings Effects with SET DEFAULT SECTION FILE SET SECTION FILE PROMPTING
(default)When you save attributes, EVE asks whether you want to save them in a section file. If you respond YES, EVE saves the attributes in your default section file. SET NOSECTION FILE PROMPTING When you save attributes, EVE saves them in your default section file without prompting you. These effects apply when you use either SAVE ATTRIBUTES or SAVE SYSTEM ATTRIBUTES or when you save attributes as part of exiting or quitting.
For more information, read the online help topic on Attributes.
SAVE ATTRIBUTES
SAVE EXTENDED EVE
SAVE SYSTEM ATTRIBUTES
The following commands set your default section file as MYSECT.TPU$SECTION in your top-level login directory and then create that section file (or a new version of that file):
Command: SET DEFAULT SECTION FILE SYS$LOGIN:MYSECT
Command: SAVE EXTENDED EVE
|
SET EXIT ATTRIBUTE CHECK
The SET EXIT ATTRIBUTE CHECK command enables attribute checking on exiting so that if you set attributes, EVE asks whether you want to save your customizations. This is the default. If SET EXIT ATTRIBUTE CHECK is in effect, then on exiting, EVE checks if you have changed attributes during the editing session and not yet saved them. If so, then EVE prompts you as follows:
Command: EXIT Attributes were changed. Save them [YES]?If you want to save your settings, press the Return key. EVE then does a SAVE ATTRIBUTES before continuing with the exit. Depending on your other settings or responses to prompts, you save them in a section file or in a DECTPU command file. If you do not want to save your settings, type NO and press Return. EVE then continues exiting.
For more information, read the online help topic on Attributes.
EXIT
QUIT
SAVE ATTRIBUTES
SAVE SYSTEM ATTRIBUTES
SET NOEXIT ATTRIBUTE CHECK
SET FILL NOTAGS
The SET FILL NOTAGS command prevents the FILL commands from wrapping lines that start with either a RUNOFF command or a VAX DOCUMENT tag. SET FILL NOTAGS adds to the list of paragraph boundaries any RUNOFF command or VAX DOCUMENT tag at the start of a line. This prevents FILL, FILL PARAGRAPH, and FILL RANGE from wrapping lines that start with those commands or tags. Blank lines and page breaks are still recognized as paragraph boundaries.The setting applies in all buffers but is not saved in a section file or command file. If you want to keep SET FILL NOTAGS for future editing sessions, put the command in an initialization file. For more information on initialization files, see the online help on Initialization Files.
SET FILL NOTAGS is the default setting in EVE.
FILL
FILL PARAGRAPH
FILL RANGE
SET FILL TAGS
SET FILL TAGS
The SET FILL TAGS command enables the FILL commands to wrap lines that start with either a RUNOFF command or a VAX DOCUMENT tag. SET FILL TAGS removes from the list of paragraph boundaries any RUNOFF command or VAX DOCUMENT tag at the start of a line. This lets FILL, FILL PARAGRAPH, and FILL RANGE wrap lines that start with those commands or tags. Blank lines and page breaks are still recognized as paragraph boundaries.If you use SET FILL TAGS, you may want to redefine FILL keys---such as GOLD-KP8 with the EDT keypad---as FILL RANGE. This avoids accidentally filling a large block of text (or an entire buffer) that does not have blank lines or page breaks, making the text hard to read or causing errors with RUNOFF or DOCUMENT processing.
The setting applies in all buffers but is not saved in a section file or command file. If you want to keep SET FILL TAGS for future editing sessions, put the command in an initialization file. For more information on initialization files, see THE online help on Initialization Files.
The default is SET FILL NOTAGS; EVE does not fill lines of text that start with a RUNOFF command or a VAX DOCUMENT tag.
FILL
FILL PARAGRAPH
FILL RANGE
SET FILL NOTAGS
SET FIND CASE EXACT
The SET FIND CASE EXACT command enables case-exact searches. This is useful to find or replace lowercase occurrences only. SET FIND CASE EXACT applies to the FIND, REPLACE, and WILDCARD FIND commands.The default is SET FIND CASE NOEXACT. EVE searches for any occurrence if you enter a string in lowercase and an exact match if you enter it in uppercase or mixed case.
The setting applies in all buffers. To save your setting, use SAVE ATTRIBUTES to create a section file or to create or update a command file. For more information, read the online help topic on Attributes.
FIND
REPLACE
SET FIND CASE NOEXACT
WILDCARD FIND
The following commands enable case-exact searches and then find the word compaq if it occurs in lowercase only:
Command: SET FIND CASE EXACT
Command: FIND compaq
|
SET FIND CASE NOEXACT
The SET FIND CASE NOEXACT command disables case-exact searches so that EVE finds any occurrence if you enter the search string in all lowercase. This is the default. SET FIND CASE NOEXACT applies to FIND, REPLACE, and WILDCARD FIND. The setting applies in all buffers. To enable case-exact searches (when you want to find or replace lowercase occurrences only) use the SET FIND CASE EXACT command.
FIND
REPLACE
SET FIND CASE EXACT
WILDCARD FIND
The following commands disable case-exact searches and then find the words compaq, COMPAQ, Compaq, or a mixed-case occurrence:
Command: SET FIND CASE NOEXACT
Command: FIND compaq
|
SET FIND NOWHITESPACE
The SET FIND NO WHITESPACE command enables FIND and WILDCARD FIND commands to match spaces and tabs exactly as specified in the search string and to search for multiword strings that do not cross lines. This is the default.If you want EVE to treat spaces, tabs, and up to one line break as "white space," use the SET FIND WHITESPACE command. Some WILDCARD FIND patterns may override the setting. For example, with OpenVMS-style wildcards, two asterisks (**) match any amount of text crossing lines and \W matches any amount of white space.
The setting applies in all buffers but is not saved in your section file or command file.
FIND
SET FIND WHITESPACE
WILDCARD FIND
In the following example, you search for Mark Twain with exactly one space between the words and entirely on one line:
Command: SET FIND NOWHITESPACE
Command: FIND Mark Twain
|
SET FIND WHITESPACE
The SET FIND WHITESPACE command enables FIND and WILDCARD FIND commands to treat spaces, tabs, and up to one line break as "white space." With SET FIND WHITESPACE, you can search for a string of two or more words, regardless of how they are separated. The default is SET FIND NOWHITESPACE. EVE matches spaces and tabs in the search string exactly, and search strings do not span a line break.The setting applies in all buffers but is not saved in a section file or command file. To keep your setting for future editing sessions, put the command in an initialization file (EVE$INIT.EVE).
FIND
SET FIND NOWHITESPACE
WILDCARD FIND
In the following example, you search for Mark Twain whether there is one or more spaces or tabs between the words or if Mark is at the end of one line and Twain at the start of the next line:
Command: SET FIND WHITESPACE
Command: FIND Mark Twain
|
SET FUNCTION KEYS NODECWINDOWS
SHOW KEY
SET FUNCTION KEYS MOTIF
The SET FUNCTION KEYS MOTIF command defines or redefines some function keys to be the same as in other Motif DECwindows applications. This is the default. SET FUNCTION KEYS MOTIF defines the keys in Table 2-9.
Table 2-9 Motif-Style Key Definitions Motif-Style Key Defined Keys CTRL/SPACE SELECT CTRL// (slash) SELECT ALL CTRL/\ (backslash) RESET CTRL/<uparrow symbol> Previous paragraph CTRL/<downarrow symbol> Next paragraph ALT/-> END OF LINE CTRL/-> EDT or WPS next word CTRL/ <- EDT or WPS previous word ALT/CTRL/-> BOTTOM ALT/ <- START OF LINE ALT/CTRL/ <- TOP CTRL/SHIFT/INSERT HERE RESTORE ALT/REMOVE Primary Cut CTRL/REMOVE EDT Delete to End of Line SHIFT/REMOVE STORE TEXT ALT/SHIFT/REMOVE Primary Copy CTRL/SHIFT/SELECT Primary Selection Restore (grab the primary selection and re-highlight EVE's previous selection) CTRL/PREV SCREEN Page Left (shift left 1 window width) CTRL/NEXT SCREEN Page Right (shift right 1 window width) SHIFT/< X| Pending Delete or EDT delete character (to the right of the cursor) This does not override any definitions of the keys, whether the EVE default, EDT keypad, WPS keypad, or definitions done with DEFINE KEY or LEARN. Learn sequences created before you enabled Motif function keys may not replay properly because the keys are now defined. To disable the keys, use the command SET FUNCTION KEYS NOMOTIF.
Shifted function keys work in DECwindows but not on character-cell terminals, such as a VT220 or VT100.
For more information about using EVE in DECwindows, see the online help topic on DECwindows Differences.
There are two ways to keep your setting for future editing sessions:
- Put the SET FUNCTION KEYS MOTIF command in an initialization file.
- Use the SAVE EXTENDED EVE command to create a section file that saves your key definitions.
SET FUNCTION KEYS NOMOTIF
SHOW KEY
SET FUNCTION KEYS NOMOTIF
The SET FUNCTION KEYS NOMOTIF command cancels Motif DECwindows-style definitions of some function keys done with the SET FUNCTION KEYS MOTIF command.There is no effect on keys you defined with DEFINE KEY or LEARN; for example, if you defined ALT/E3, your definition overrides the Motif function key definition.
Learn sequences that use DECwindows-style function keys may not replay properly because the keys are now undefined or defined differently.
SET FUNCTION KEYS MOTIF
SHOW KEY
SET GOLD KEY keyname
keyname
The key you want to set as GOLD. If you do not specify a key name, EVE prompts you to press the key you want to define. Pressing the Return key or Ctrl/M at the prompt cancels the operation because those keys cannot be redefined.
The SET GOLD KEY command defines a key as the GOLD key for use with other keys, and enables several GOLD key sequences. The GOLD key increases the possible key bindings. For example, you can define F20 to execute one command and define GOLD-F20 to execute another command. To execute one function, you press F20 alone; to execute the other function, you press GOLD and then press F20. You can also define combinations of GOLD and a typing key, such as GOLD-C.Setting the GOLD key, by itself or by setting the EDT or WPS keypad, automatically defines some GOLD sequences for the arrow keys and the minikeypad, unless you have defined the keys otherwise. Table 2-10 lists the default GOLD sequences. Some of these require a VT300- or VT200-series terminal (for example, GOLD-Help).
Table 2-10 EVE Default GOLD Key Sequencess EVE Default Keys Defined Keys GOLD-F13 RESTORE WORD or WPS Delete Beginning Sentence GOLD-Help HELP KEYS (list) GOLD-Find WILDCARD FIND GOLD-Insert Here RESTORE GOLD-Remove STORE TEXT GOLD-Select RESET GOLD-Prev Screen PREVIOUS WINDOW GOLD-Next Screen NEXT WINDOW GOLD-<uparrow symbol> TOP GOLD- <- START OF LINE GOLD-<downarrow symbol> BOTTOM GOLD--> END OF LINE SET GOLD KEY overrides any current definition of the key you specify, whether the key is defined by EVE, the EDT keypad, the WPS keypad, or a definition of your own. You can have only one key set as GOLD at a time. The EDT or WPS keypad makes PF1 the GOLD key, overriding any current definition of PF1. However, if you set a different key as the GOLD key, then the EDT or WPS keypad uses your GOLD key. In such a case, using the SET NOGOLD KEY command cancels your GOLD key and restores PF1 as the GOLD key for the EDT or WPS keypad.
Key definitions remain in effect throughout your editing session or until you redefine or undefine the keys. There are two ways to keep your GOLD key and other key definitions for future editing sessions:
- Put SET GOLD KEY and other key-definition commands in an initialization file (EVE$INIT.EVE).
- Use the SAVE EXTENDED EVE command to create a section file that saves your key definitions.
DEFINE KEY
SET NOGOLD KEY
SHOW KEY
UNDEFINE KEY
The following commands set PF1 as the GOLD key, and then define the combination of GOLD and the letter C as the CENTER LINE command. Typing a C or c by itself still inserts that letter. In specifying a GOLD key sequence, use a dash, slash, or underscore as a delimiter in the key name.
Command: SET GOLD KEY PF1
Command: DEFINE KEY= GOLD-C CENTER LINE
|
SET JOURNALING buffer
buffer
The buffer for which you want to create a buffer-change journal file. If you do not specify a file name, EVE prompts for one. Pressing the Return key or the Do key at the prompt without typing anything cancels the operation.
The SET JOURNALING command enables buffer-change journaling for the buffer you specify, creating a journal file. By default, EVE creates a buffer-change journal file for each text buffer you create. Therefore, you would use the SET JOURNALING command only if you had disabled journaling either by invoking EVE with the /NOJOURNAL qualifier or by using the SET NOJOURNALING command during your editing session.The journal file name derives from the name of the buffer or file you are editing and the file type .TPU$JOURNAL. For example, if you edit a file named MEMO.TXT, the journal file is called MEMO_TXT.TPU$JOURNAL.
The journal file is created in the directory defined by the TPU$JOURNAL logical name. The default is SYS$SCRATCH, which is your top-level login directory.
To check the journal file name for the buffer, use the SHOW command.
You cannot enable journaling for a buffer that is modified. First write out the buffer (by using WRITE FILE or SAVE FILE), and then enable journaling.
To enable journaling for all your buffers, use the SET JOURNALING ALL command.
RECOVER BUFFER
SET JOURNALING ALL
SET NOJOURNALING
SHOW
The following example enables buffer-change journaling for a buffer called TEST DATA. EVE then creates a journal file named TEST_ DATA.TPU$JOURNAL.
Command: SET JOURNALING TEST DATA
|
SET JOURNALING ALL
The SET JOURNALING ALL command enables buffer-change journaling for all your text buffers. By default, EVE creates a journal file for each text buffer you create. Use the SET JOURNALING ALL command only if you had disabled journaling either by invoking EVE with the /NOJOURNAL qualifier or by using the SET NOJOURNALING ALL command during your editing session.To check the journal file name for the current buffer, use the SHOW command.
You cannot enable journaling for buffers that are modified. First write out the buffers by using WRITE FILE or SAVE FILE, and then enable journaling.
RECOVER BUFFER
SET JOURNALING
SET NOJOURNALING ALL
SHOW
| Previous | Next | Contents | Index |
|
|
| privacy and legal statement | ||
| 6021PRO_010.HTML | ||