Termcap is a software library and database used on Unix-like computers. It enables programs to use display computer terminals in a device-independent manner, which greatly simplifies the process of writing portable text mode applications. Bill Joy wrote the first termcap library for the Berkeley Unix operating system; it has since been ported to most Unix and Unix-like environments. Joy's design was reportedly influenced by the design of the terminal data store in the earlier Incompatible Timesharing System system.
A termcap database can describe the capabilities of hundreds of different display terminals. This allows external programs to be able to have character-based display output, independent of the type of terminal. On-screen text editors such as vi and emacs are examples of programs that may use termcap. Other programs are listed in the Termcap category.
Examples of what the database describes:
- how many columns wide it is
- what string to send to move the cursor to an arbitrary position (including how to encode the row and column numbers)
- how to scroll the screen up one or several lines
- how much padding is needed for such a scrolling operation.
Data modelTermcap databases consist of one or more descriptions of terminals.
IndicesEach description must contain the canonical name of the terminal. It may also contain one or more aliases for the name of the terminal. The canonical name or aliases are the keys by which the library searches the termcap database.
Data ValuesThe description contains one or more capabilities, which have conventional names. The capabilities are typed: boolean, numeric and string. The termcap library has no predetermined type for each capability name. It determines the types of each capability by the syntax:
- string capabilities have an "=" between the capability name and its value,
- numeric capabilities have a "#" between the capability name and its value, and
- boolean capabilities have no associated value (they are always true if specified).
Applications which use termcap do expect specific types for the commonly used capabilities, and obtain the values of capabilities from the termcap database using library calls that return successfully only when the database contents matches the assumed type.
HierarchyTermcap descriptions can be constructed by including the contents of one description in another, suppressing capabilities from the included description or overriding or adding capabilities. No matter what storage model is used, the termcap library constructs the terminal description from the requested description, including, suppressing or overriding at the time of the request.
Storage ModelTermcap data is stored as text, making it simple to modify. The text can be retrieved by the termcap library from files or environment variables.
Environment VariableThe TERMCAP environment variable may contain a termcap database. It is most often used to store a single termcap description, set by a terminal emulator to provide the terminal's characteristics to the shell and dependent programs.
Flat FileThe original (and most common) implementation of the termcap library retrieves data from a flat text file. Searching a large termcap file, e.g., 500Kb, can be slow. To aid performance, a utility such as reorder is used to put the most frequently used entries near the beginning of the file.
Hashed DatabaseNewer implementations of termcap store the terminal description in a hashed database, e.g., something like Berkeley DB version 1.85. These store two types of records: aliases which point to the canonical entry, and the canonical entry itself. The text of the termcap entry is stored literally.
Limitations and ExtensionsThe original termcap implementation was designed to use little memory:
- the first name is two characters, to fit in 16 bits
- capability names are two characters
- descriptions are limited to 1023 characters.
- only one description can be included, and must be at the end.
Newer implementations of the termcap interface generally do not require the two-character name at the beginning of the entry.
Capability names are still two characters in all implementations.
The tgetent function used to read the terminal description uses a buffer whose size must be large enough for the data, and is assumed to be 1024 characters. Newer implementations of the termcap interface may relax this constraint by allowing a null pointer in place of the fixed buffer , or by hiding the data which would not fit, e.g., via the ZZ capability in NetBSD termcap.
The terminfo library interface also emulates the termcap interface, and does not actually use the fixed-size buffer.
The terminfo library's emulation of termcap allows multiple descriptions to be included without restricting the position. A few other newer implementations of the termcap library may also provide this ability, though it is not well-documented.