tic(1M) DG/UX 5.4.2 tic(1M)
NAME
tic - TERMINFO compiler
SYNOPSIS
tic [-c] [ -v[n] ] file
where:
n An integer from 1 to 10 inclusive, indicating the level of
detail desired
file The path to a terminfo(4) source file
DESCRIPTION
The tic command translates a TERMINFO file from a textual source
format into a binary compiled format. The compiled format is
necessary for use with the library routines described in curses(3X).
The single file argument specifies the pathname of a file containing
one or more TERMINFO terminal descriptions in source format (see
terminfo(4)). Each description in the file describes the
capabilities of a particular terminal.
By default, the resulting binary files are placed under the directory
/usr/share/lib/terminfo. However, if the environment variable
TERMINFO is set, the compiled results are placed under the directory
specified by the value of that variable.
When a use=entry-name field is discovered in a terminal entry
currently being compiled, tic reads in the binary entry-name file to
complete the entry. Tic duplicates the capabilities in entry-name
for the current entry, with the exception of those capabilities that
are explicitly defined in the current entry. If entry-name is
created within the same source file, tic will compile and write out
entry-name before reading it back in to satisfy the use=entry-name
field. This ordering is guaranteed regardless of the organization of
the source file; tic performs dependency analysis on the definitions
in file, and compiles entries in an order that satisfies the use=
dependencies. If entry-name is not found within file, tic will first
search the directory named by the environment variable TERMINFO, if
that variable is set. If entry-name is not found there (or if
TERMINFO is not set), tic will then search the default directory
/usr/share/lib/terminfo.
Options are:
-vn specify that (verbose) trace information be written to
standard error showing tic's progress. If n is omitted, the
default level is 1. If n is specified and greater than 1, the
level of detail is increased.
-c check file for errors only; do not write out compiled entries.
Errors in use= links are not detected.
FILES
/usr/share/lib/terminfo/?/*
compiled terminal description data base
Licensed material--property of copyright holder(s) 1
tic(1M) DG/UX 5.4.2 tic(1M)
DIAGNOSTICS
Parse Errors
All parser error messages are prefixed by the approximate line number
of the error and the title of the entry being processed.
File does not start with terminal names in column one
The first line encountered in the file, after comments, must be a
list of terminal names.
´termname': bad first term name.
or
´termname': bad term name found in list.
or
Illegal terminal name - 'termname'
Terminal names must start with a letter or digit,
The terminal name termname was invalid. Names must not contain white
space or slashes, and must begin with a letter or digit.
´termname': terminal name too long.
An extremely long terminal name termname was found.
´termname': terminal name too short.
A one-character terminal name termname was found.
At least one synonym should begin with a letter.
None of the names for the terminal began with a letter.
Newline in middle of terminal name
The trailing comma was probably left off of the list of names.
termname: bad term name
The current entry specifies an invalid terminal name in the
use=termname field.
´termname' defined in more than one entry.
An entry termname was defined more than once in the same source file.
Terminal name 'termname' synonym for itself
A terminal name termname was also listed in its list of synonyms.
Unknown Capability - 'capname'
The capability capname was found within the file but is not a
recognized terminfo(4) variable.
Licensed material--property of copyright holder(s) 2
tic(1M) DG/UX 5.4.2 tic(1M)
Wrong type used for capability 'capname'
A boolean capability was given a value, a numeric capability was
given a string value, or a string capability was given a numeric
value.
Unknown token type
The character following a capability was not one of the four allowed:
, for boolean capabilities, # for numeric capabilities, = for string
capabilities, or @ to cancel any type of capability.
Illegal character - 'char'
The invalid character char was found in the input file.
Illegal ^ character - 'char'
The second character of a control sequence specification ^char was
not a printable ASCII character.
Illegal character in \ sequence - 'char'
The second character of a backslash escape sequence \char did not
result in a recognized terminfo(4) special sequence.
Missing comma
A comma was missing.
Missing numeric value
A numeric capability was not followed by any number.
NULL string value
A string capability was not followed by any string. (The proper way
to delete a string capability is to use the cancel token @.)
Very long string found. Missing comma?
A string capability has a very long value. This is usually caused by
a missing comma.
Premature EOF
The current entry ended prematurely, indicating a syntax error.
Premature EOF - missing comma?
The current entry contained an unterminated string capability. This
is usually caused by a missing comma.
Token after a seek not NAMES
Licensed material--property of copyright holder(s) 3
tic(1M) DG/UX 5.4.2 tic(1M)
The file being compiled was changed during the compilation.
Backspaced off beginning of line
An internal error in tic has been detected.
Error in following up use-links.
A use=name capability either referenced a non-existent terminal
called name, or name somehow referred back to the current entry. A
list of entries involved is printed following the error message.
Other Errors
A command line error results in a self-explanatory message
identifying the problem, followed by a usage summary for the tic
command. A system call failure results in a message identifying the
system operation that failed, as well as the approximate line number
and the title of the entry being processed, where appropriate.
SEE ALSO
captoinfo(1M), infocmp(1M), curses(3X), terminfo(4), term(5).
NOTES
Compiled entries cannot exceed 4096 bytes. The name field cannot
exceed 128 bytes.
When the -c option is used, duplicate terminal names will not be
diagnosed; however, when -c is not used, they will be.
When an entry, for instance entryname1, contains a use=entryname2
field, any canceled capabilities in entryname2 must also appear in
entryname1 before the use= field, if these capabilities are to be
canceled in entryname1.
Licensed material--property of copyright holder(s) 4