-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<!--
****************************************************************************
- * Copyright (c) 1998-2002,2003 Free Software Foundation, Inc. *
+ * Copyright (c) 1998-2011,2017 Free Software Foundation, Inc. *
* *
* Permission is hereby granted, free of charge, to any person obtaining a *
* copy of this software and associated documentation files (the *
* sale, use or other dealings in this Software without prior written *
* authorization. *
****************************************************************************
- * @Id: term.7,v 1.14 2003/05/10 20:33:49 jmc Exp @
+ * @Id: term.7,v 1.24 2017/02/18 17:01:51 tom Exp @
-->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
<HTML>
<HEAD>
-<TITLE>TERM 7</TITLE>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="Manpage converted by man2html - see http://invisible-island.net/scripts/readme.html#others_scripts">
+<TITLE>term 7</TITLE>
<link rev=made href="mailto:bug-ncurses@gnu.org">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</HEAD>
<BODY>
-<H1>TERM 7</H1>
-<HR>
+<H1 class="no-header">term 7</H1>
<PRE>
-<!-- Manpage converted by man2html 3.0.1 -->
-<STRONG><A HREF="TERM.7.html">TERM(7)</A></STRONG> <STRONG><A HREF="TERM.7.html">TERM(7)</A></STRONG>
+<STRONG><A HREF="term.7.html">term(7)</A></STRONG> <STRONG><A HREF="term.7.html">term(7)</A></STRONG>
-</PRE>
-<H2>NAME</H2><PRE>
+</PRE><H2><a name="h2-NAME">NAME</a></H2><PRE>
term - conventions for naming terminal types
-</PRE>
-<H2>DESCRIPTION</H2><PRE>
+</PRE><H2><a name="h2-DESCRIPTION">DESCRIPTION</a></H2><PRE>
The environment variable <STRONG>TERM</STRONG> should normally contain the
type name of the terminal, console or display-device type
you are using. This information is critical for all
mailer.
A default <STRONG>TERM</STRONG> value will be set on a per-line basis by
- either <STRONG>/etc/inittab</STRONG> (Linux and System-V-like UNIXes) or
+ either <STRONG>/etc/inittab</STRONG> (e.g., System-V-like UNIXes) or
<STRONG>/etc/ttys</STRONG> (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.
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 <STRONG>TERM</STRONG> set-
the tty device and baud rate.
Setting your own <STRONG>TERM</STRONG> 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
from your shell. These capability files are in a binary
format optimized for retrieval speed (unlike the old text-
based <STRONG>termcap</STRONG> format they replace); to examine an entry,
- you must use the <STRONG><A HREF="infocmp.1.html">infocmp(1)</A></STRONG> command. Invoke it as fol-
+ you must use the <STRONG><A HREF="infocmp.1m.html">infocmp(1m)</A></STRONG> command. Invoke it as fol-
lows:
- infocmp <EM>entry-name</EM>
+ infocmp <EM>entry</EM><STRONG>_</STRONG><EM>name</EM>
- where <EM>entry-name</EM> is the name of the type you wish to exam-
+ where <EM>entry</EM><STRONG>_</STRONG><EM>name</EM> 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 <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>.
The first line of a <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG> 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 <EM>primary</EM>
<EM>name</EM>, and is the one to use when setting <STRONG>TERM</STRONG>. The last
thus <STRONG>vt100</STRONG>, <STRONG>hp2621</STRONG>, <STRONG>wy50</STRONG>.
The root name for a PC-Unix console type should be the OS
- name, i.e. <STRONG>linux</STRONG>, <STRONG>bsdos</STRONG>, <STRONG>freebsd</STRONG>, <STRONG>netbsd</STRONG>. It should <EM>not</EM>
+ name, i.e., <STRONG>linux</STRONG>, <STRONG>bsdos</STRONG>, <STRONG>freebsd</STRONG>, <STRONG>netbsd</STRONG>. It should <EM>not</EM>
be <STRONG>console</STRONG> 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. <STRONG>versaterm</STRONG>, <STRONG>ctrm</STRONG>).
+ 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., <STRONG>versaterm</STRONG>, <STRONG>ctrm</STRONG>).
Following the root name, you may add any reasonable number
of hyphen-separated feature suffixes.
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
- <STRONG>fubar-30-rv</STRONG> (rather than, say, `fubar-rv-30').
+ <STRONG>fubar-30-rv</STRONG> (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
environment variable when no -T option is specified.
-</PRE>
-<H2>PORTABILITY</H2><PRE>
+</PRE><H2><a name="h2-PORTABILITY">PORTABILITY</a></H2><PRE>
For maximum compatibility with older System V UNIXes,
names and aliases should be unique within the first 14
characters.
-</PRE>
-<H2>FILES</H2><PRE>
+</PRE><H2><a name="h2-FILES">FILES</a></H2><PRE>
/usr/share/terminfo/?/*
compiled terminal capability data base
tty line initialization (BSD-like UNIXes)
-</PRE>
-<H2>SEE ALSO</H2><PRE>
+</PRE><H2><a name="h2-SEE-ALSO">SEE ALSO</a></H2><PRE>
<STRONG><A HREF="ncurses.3x.html">curses(3x)</A></STRONG>, <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>, <STRONG><A HREF="term.5.html">term(5)</A></STRONG>.
- <STRONG><A HREF="TERM.7.html">TERM(7)</A></STRONG>
+ <STRONG><A HREF="term.7.html">term(7)</A></STRONG>
</PRE>
-<HR>
-<ADDRESS>
-Man(1) output converted with
-<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
-</ADDRESS>
+<div class="nav">
+<ul>
+<li><a href="#h2-NAME">NAME</a></li>
+<li><a href="#h2-DESCRIPTION">DESCRIPTION</a></li>
+<li><a href="#h2-PORTABILITY">PORTABILITY</a></li>
+<li><a href="#h2-FILES">FILES</a></li>
+<li><a href="#h2-SEE-ALSO">SEE ALSO</a></li>
+</ul>
+</div>
</BODY>
</HTML>