X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fterm.7.html;h=ceb5528f5d30d35eda50139ec09c72a1a1c0557c;hp=85284e7d847d368be8461ff11e49ddb92d5f5b8c;hb=ce4803687b821efbc5fb2c5a5f06d69cd4dc2656;hpb=a8987e73ec254703634802b4f7ee30d3a485524d diff --git a/doc/html/man/term.7.html b/doc/html/man/term.7.html index 85284e7d..ceb5528f 100644 --- a/doc/html/man/term.7.html +++ b/doc/html/man/term.7.html @@ -1,7 +1,6 @@ - +
-- -TERM(7) TERM(7) +term(7) term(7) --
+
term - conventions for naming terminal types --
+
The environment variable TERM should normally contain the type name of the terminal, console or display-device type you are using. This information is critical for all @@ -59,14 +57,14 @@ mailer. A default TERM value will be set on a per-line basis by - either /etc/inittab (Linux and System-V-like UNIXes) or + either /etc/inittab (e.g., System-V-like UNIXes) or /etc/ttys (BSD UNIXes). This will nearly always suffice for workstation and microcomputer consoles. If you use a dialup line, the type of device attached to it may vary. Older UNIX systems pre-set a very dumb ter- - minal type like `dumb' or `dialup' on dialup lines. Newer - ones may pre-set `vt100', reflecting the prevalence of DEC + minal type like "dumb" or "dialup" on dialup lines. Newer + ones may pre-set "vt100", reflecting the prevalence of DEC VT100-compatible terminals and personal-computer emula- tors. @@ -75,7 +73,7 @@ if the remote terminfo or termcap entry for your type is not compatible with yours, but this situation is rare and can almost always be avoided by explicitly exporting - `vt100' (assuming you are in fact using a VT100-superset + "vt100" (assuming you are in fact using a VT100-superset console, terminal, or terminal emulator.) In any case, you are free to override the system TERM set- @@ -85,9 +83,9 @@ the tty device and baud rate. Setting your own TERM value may also be useful if you have - created a custom entry incorporating options (such as - visual bell or reverse-video) which you wish to override - the system default type for your line. + created a custom entry incorporating options (such as vis- + ual bell or reverse-video) which you wish to override the + system default type for your line. Terminal type descriptions are stored as files of capabil- ity data underneath /usr/share/terminfo. To browse a list @@ -98,19 +96,19 @@ from your shell. These capability files are in a binary format optimized for retrieval speed (unlike the old text- based termcap format they replace); to examine an entry, - you must use the infocmp(1) command. Invoke it as fol- + you must use the infocmp(1m) command. Invoke it as fol- lows: - infocmp entry-name + infocmp entry_name - where entry-name is the name of the type you wish to exam- + where entry_name is the name of the type you wish to exam- ine (and the name of its capability file the subdirectory of /usr/share/terminfo named for its first letter). This command dumps a capability file in the text format described by terminfo(5). The first line of a terminfo(5) description gives the - names by which terminfo knows a terminal, separated by `|' + names by which terminfo knows a terminal, separated by "|" (pipe-bar) characters with the last name field terminated by a comma. The first name field is the type's primary name, and is the one to use when setting TERM. The last @@ -152,16 +150,16 @@ thus vt100, hp2621, wy50. The root name for a PC-Unix console type should be the OS - name, i.e. linux, bsdos, freebsd, netbsd. It should not + name, i.e., linux, bsdos, freebsd, netbsd. It should not be console or any other generic that might cause confusion in a multi-platform environment! If a model number fol- lows, it should indicate either the OS release level or the console driver release level. - The root name for a terminal emulator (assuming it doesn't - fit one of the standard ANSI or vt100 types) should be the - program name or a readily recognizable abbreviation of it - (i.e. versaterm, ctrm). + The root name for a terminal emulator (assuming it does + not fit one of the standard ANSI or vt100 types) should be + the program name or a readily recognizable abbreviation of + it (i.e., versaterm, ctrm). Following the root name, you may add any reasonable number of hyphen-separated feature suffixes. @@ -202,7 +200,7 @@ intended to specify a line height, that suffix should go first. So, for a hypothetical FuBarCo model 2317 terminal in 30-line mode with reverse video, best form would be - fubar-30-rv (rather than, say, `fubar-rv-30'). + fubar-30-rv (rather than, say, "fubar-rv-30"). Terminal types that are written not as standalone entries, but rather as components to be plugged into other entries @@ -215,15 +213,13 @@ environment variable when no -T option is specified. --
+
For maximum compatibility with older System V UNIXes, names and aliases should be unique within the first 14 characters. --
+
/usr/share/terminfo/?/* compiled terminal capability data base @@ -234,18 +230,21 @@ tty line initialization (BSD-like UNIXes) --
+
curses(3x), terminfo(5), term(5). - TERM(7) + term(7)-