ULTRIX Differences
Most EVE commands and keys work the same on VMS and ULTRIX. Here is a list
of important differences:
Features Effects or differences on ULTRIX
----------------------------------------------------------------------
File names On ULTRIX, file names are case-sensitive---for
example, MEMO.TXT and memo.txt are different files. On
VMS, file names are not case-sensitive.
Backup files If you write a buffer or save a section file to an
existing file, EVE first copies the existing file to a
backup file before overwriting the existing file. EVE
appends a version number to the default name of the
backup file that increments with each new backup file.
The user can disable the feature, or customize the way
EVE creates the backup file spec by using the SET
NOFILE BACKUP or SET BACKUP CONTROL STRING commands.
VMS has file version numbers that are automatically
provided by the file system.
Buffer names On ULTRIX, buffer names are case-sensitive---for
example, TEMP and temp specify different buffers. EVE
system buffers are named in uppercase (for example,
MESSAGES, INSERT HERE, $RESTORE$, and so on). On VMS,
buffer names are not case-sensitive.
Journaling On ULTRIX, buffer-change journal files are created in
your current, working directory. Default file type is
.tpu_journal. You cannot have two buffer-change
journal files of the same name. If there is a
MAIN.tpu_journal file from an previous editing
session, the MAIN buffer in the current editing
session will not be journaled. For more information,
see help on Journal Files.
Wildcards Default wildcards match the system you are using.
Thus, on VMS, the default is SET WILDCARD VMS; on
ULTRIX, it is SET WILDCARD ULTRIX. The setting applies
only to WILDCARD FIND and SHOW WILDCARDS---it does not
affect wildcards in file names, which are determined
by the operating system.
SHELL or DCL The SHELL and DCL commands are synonyms appropriate to
the operating system you are using. Thus, on ULTRIX,
you can use SHELL or DCL to execute a command for the
command shell (such as ls to get get a list of files).
Similarly, on VMS systems, you can use DCL or SHELL to
execute a command like as DIRECTORY. For example, the
following commands are equivalent---listing in a
single column the files in your current, default
directory:
On ULTRIX On VMS
----------- --------------------
SHELL ls -1 DCL DIRECTORY /COL=1
(For more information, see help on the DCL command.)
CTRL/D exit On ULTRIX systems, EVE defines CTRL/D (as well as
CTRL/Z and F10) as EXIT (ending the editing session).
On VMS systems, EVE does not define CTRL/D. Other EVE
keys are defined the same on both systems.
Startup files On ULTRIX, if you do not specify a command,
initialization, or section file, EVE and TPU look for
the following default startup files in the order
given:
Init file ......... ./eve_init.eve
......... ~./eve_init.eve
Command file ...... ./tpu_command.tpu
Section file ...... ./tpu_section.tpu_section
...... /usr/lib/tpu/\
...... tpu_section.tpu_section
Note that on ULTRIX, you cannot define logical names
for startup files.
File defaults On ULTRIX, if EVE and TPU cannot find the exact file
you specify on the shell command line for the section,
debug, command, and initialization files, then they
will apply one or more VMS-style defaults to your file
specification, and look again. No directory defaults
will be applied if you specify a directory component.
The following are the default file specifications that
are applied in the order given:
Init file ......... eve_init.eve
......... ~/
......... ~/eve_init.eve
Debug file ....... tpu_debug.tpu
......... /usr/lib/tpu/
......... /usr/lib/tpu/tpu_debug.tpu
Command file ...... tpu_command.tpu
Section file ...... tpu_section.tpu_section
......... /usr/lib/tpu/
......... /usr/lib/tpu/\
.......... tpu_section.tpu_section
Options In invoking EVE, command-line options are positional
(they must come before the input files, if any) and do
not use an equal sign (=) to distinguish a file
associated with an option and the input file or files.
For example, the following command invokes EVE using
an initialization file named myinit.eve to edit a file
named memo.txt:
% tpu -i myinit memo.txt
For more information, see the EVE Reference Manual or
DEC Text Processing Utility Manual.
DECwindows On ULTRIX, to invoke EVE with the Motif DECwindows
interface, use the dmtpu command.
SPELL The SPELL command on ULTRIX does not modify your text,
but simply produces a list of any misspelled words in
a second window. The SPELL command on VMS lets you
modify your text by spawning a subprocess in which you
interact with the VMS DECspell utility. When you exit
DECspell, your text is modified with the spelling
corrections.
Environment Variables
On ULTRIX you can set the EVEKEYPAD environment
variable to select an EVE keypad. Valid names are EDT,
EVE, NUMERIC, VT100, and WPS. If you do not set the
environment variable, the keypad defaults to EVE which
gives the VT100 keypad on VT100 terminals or the
NUMERIC keypad on VT200 and later terminals.
If you are accustomed to pressing CTRL/L to refresh (redraw) the screen,
you can redefine CTRL/L as REFRESH. By default, EVE defines CTRL/W as
REFRESH and defines CTRL/L as INSERT PAGE BREAK.
If you are accustomed to the vi editor, you may want to define the ESCAPE
key or CTRL/[ (left bracket) as DO to emulate vi. However, on VMS systems,
EVE does not let you define ESCAPE or CTRL/[.
If you are accustomed to pressing CTRL/Z to exit the editor (ending the
editing session), you should instead use the CTRL/D key when using
character cell EVE on ULTRIX. The CTRL/Z key on ULTRIX systems usually
suspends your process, and turns control over to the shell, requiring you
to enter the fg (foreground) command to resume editing. EVE defines CTRL/D
as EXIT on ULTRIX systems to help you avoid this problem. This problem
does not occur with DECwindows EVE where the CTRL/Z key exits the editor.
For more information about EVE and TPU, see the EVE Reference Manual and
DEC Text Processing Utility Manual.
+----------------------------------------------------------------+
| You can create a section file on VMS and use it on ULTRIX (or |
| conversely). However some procedures and key definitions may |
| not work or may not work properly if they use system-specific |
| features or differences, such as file names and directories. |
+----------------------------------------------------------------+
Related topics:
Defaults Journal Files VMS Differences