Annotation of researchv10no/ncurses/terminfo/header, revision 1.1.1.1

1.1       root        1: # ------------------------
                      2: #      @(#)header      1.3
                      3: #      Terminfo source file @(#)header 1.1 (CBOSGD) 12/28/82
                      4: #      U.C. Berkeley, Bell Telephone Laboratories
                      5: #
                      6: # This file describes capabilities of various terminals, as needed by
                      7: # software such as screen editors.  It does not attempt to describe
                      8: # printing terminals very well, nor graphics terminals.  Someday.
                      9: # See terminfo(4) in the Unix Programmers Manual for documentation.
                     10: # Terminfo was developed from termcap. Termcap is based on software
                     11: # developed at U.C. Berkeley.
                     12: #
                     13: # Conventions: First entry is two chars, first char is manufacturer,
                     14: # second char is canonical name for model or mode.
                     15: # Third entry is the one the editor will print with "set" command.
                     16: # Last entry is verbose description.
                     17: # Others are mnemonic synonyms for the terminal.
                     18: #
                     19: # Terminal naming conventions:
                     20: # Terminal names look like <manufacturer> <model> - <modes/options>
                     21: # Certain abbreviations (e.g. c100 for concept100) are also allowed
                     22: # for upward compatibility.  The part to the left of the dash, if a
                     23: # dash is present, describes the particular hardware of the terminal.
                     24: # The part to the right can be used for flags indicating special ROM's,
                     25: # extra memory, particular terminal modes, or user preferences.
                     26: # All names are always in lower case, for consistency in typing.
                     27: # Because of file naming restrictions, terminal names should not contain
                     28: # period or slash, in fact, entirely alphanumeric characters plus dash are
                     29: # highly recommended.  These restrictions do not apply to the verbose name.
                     30: #
                     31: # The following are conventionally used flags:
                     32: #      rv      Terminal in reverse video mode (black on white)
                     33: #      2p      Has two pages of memory.  Likewise 4p, 8p, etc.
                     34: #      w       Wide - in 132 column mode.
                     35: #      pp      Has a printer port which is used.
                     36: #      na      No arrow keys - terminfo ignores arrow keys which are
                     37: #              actually there on the terminal, so the user can use
                     38: #              the arrow keys locally.
                     39: #      #       The number of lines on the screen.
                     40: #      s       With a status line.
                     41: #  
                     42: # There are some cases where the same name is used for two different
                     43: # terminals, e.g. "teleray" or "2621" or "vt100".  In these cases,
                     44: # if a site has one of these, they should choose a local default and
                     45: # bring that terminal to the front in the reorder script.  This works
                     46: # because tgetent picks the first match in /usr/lib/terminfo.
                     47: #
                     48: # If you absolutely MUST check for a specific terminal (this is discouraged)
                     49: # check for the 1st entry (the canonical form) since all other codes are
                     50: # subject to change.  We would much rather put in special capabilities to
                     51: # describe your terminal rather than having you key on the name.

unix.superglobalmegacorp.com

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.