contents.gifprev1.gifnext1.gif

Defaults File

UNIX: /usr/local/nu_tpu/nu_tpu.def

DOS: c:\nu_tpu\nu_tpu.def

VMS: none

Defaults files override the pre-programmed nu/TPU runtime environment settings. Defaults files provide an easy means for users and system managers to define personal and site-wide nu/TPU settings by modifying a single text file. The defaults file’s syntax provides for a single keyword setting per line. The keyword must start in the first column and be terminated by a colon. Immediate- ly after the colon is the new value for the keyword. Spaces and tabs are not allowed before or after the colon separating the keyword and its value. The text for the new value can be terminated with a colon or a space character. White space is not allowed until the end of the KEYWORD value. Pound signs, ‘#’, are used to indicate comments in the defaults file. If a line contains a pound sign, all text to the right of the pound sign is considered a comment. For Boolean settings, 1 and 0 are used for indicating TRUE and FALSE respectively.

Defaults files may be nested by using the TPU_DEFAULTS_ FILE keyword and providing the path and filename for another nu/TPU defaults file. The default’s filename is nu_tpu.def, located in the TPU_HOME/ nu_tpu or user’s home directory. The location and filename of the defaults file may be overridden by setting the TPU_DEFAULTS_FILE environment variable. If ambiguous or contradictory defaults are set, only the latest is used. Remember that environment variables and nu/TPU command line options always take precedence over defaults file values.

Sample nu/TPU System Defaults File

This listing contains all the defaults file KEYWORDS that are available for modification, along with their internal nu/TPU default settings.

# Command Line Options

COMMAND_FILE: common/tpuini.tpu: # Execute at startup.

CREATE:1: # Create edit file if not found.

DEBUG_FILE: common/debug.tpu: # Supplied debug tpu code.

DISPLAY:1 # Send output to supported terminal.

ENVIRONMENT:0 # Show nu/TPU runtime settings.

INITIALIZATION_FILE: si_init.si: # Execute during EVE startup.

JOURNAL_FILE:: # User_file.tjl

MODIFY:0: # Allow changes to main buffer.

OUTPUT_FILE:: # Default user_file.

READ_ONLY:0: # Allow updates to main buffer.

RECOVER:0: # If TRUE, attempt edit session recovery

SECTION_FILE: si.sec: # Active section file.

START_CHARACTER:1: # Position cursor at column.

START_RECORD:1: # Position cursor at record.

WRITE:1: # Allow output of main buffer.

# Operating System Options

ABORT_2_CONTROL_C:1: # Abort nu/TPU with two consecutive

# Ctrl-C presses.

BACKUPS:1: # Number of backup versions.

FILE_STYLE:UNIX: # Syntax of file specs: DOS/UNIX/VMS.

HANDLE_ESCAPE:: # Allow use of escape key.

HOME:~: # Directory specification for home directory.

KEYBOARD:vt200: # Any nu/TPU keyboard device.

LENGTH:24: # Length of window.

STACK_SIZE:1000: # nu/TPU internal stack size.

SWITCH_STYLE:-: # Command line option separator.

TPU_DEFAULTS_FILE: nu_tpu.def: # Active defaults file.

WIDTH:80: # Width of the window.

The following two defaults files provide an example of site-wide settings being augmented with an end user’s personal defaults file.

# ABC Corps site-wide nu/TPU defaults file. /usr/local/nu_tpu.def

# Command Line Options

COMMAND_FILE: common/abc_corp.tpu:

SECTION_FILE: abc_corp.ini: # Section file in nu_tpu/common.

# Operating system options

KEYBOARD:vt200: # Any nu/TPU keyboard device.

SWITCH:-: # Command line option separator.

# My defaults files. First take the site-wide defaults, then

# override settings to access personal customizations. Filename

# /nu_tpu.def

TPU_DEFAULTS_FILE:/usr/local/nu_tpu.def: # Take initial site default settings.

INITIALIZATION_FILE:two_wins.int # Split edit window.

SECTION_FILE:my_edt.ini: # Use preset EDT setup.

START_RECORD:10: # Position cursor at 10th line of text.

nu/TPU will search for a defaults file in the following sequence until a file match is located or all possibilities have been exhausted. If the TPU_ DEFAULTS_FILE environment variable is set, its file specification is searched. Next, the end user’s home directory is searched for file nu_tpu.def. Lastly, the TPU_HOME/nu_tpu directory is searched for nu_tpu.def. Also see the section on environment variables for additional information on nu/TPU setup issues.