diff options
Diffstat (limited to 'doc/html/man/term.7.html')
| -rw-r--r-- | doc/html/man/term.7.html | 90 |
1 files changed, 43 insertions, 47 deletions
diff --git a/doc/html/man/term.7.html b/doc/html/man/term.7.html index 9a8858878771..b119732c8a2c 100644 --- a/doc/html/man/term.7.html +++ b/doc/html/man/term.7.html @@ -1,6 +1,6 @@ <!-- **************************************************************************** - * Copyright 2018-2023,2024 Thomas E. Dickey * + * Copyright 2018-2024,2025 Thomas E. Dickey * * Copyright 1998-2011,2017 Free Software Foundation, Inc. * * * * Permission is hereby granted, free of charge, to any person obtaining a * @@ -27,25 +27,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: term.7,v 1.48 2024/03/16 15:35:01 tom Exp @ + * @Id: term.7,v 1.52 2025/08/16 20:08:21 tom Exp @ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <HTML> <HEAD> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <meta name="generator" content="Manpage converted by man2html - see https://invisible-island.net/scripts/readme.html#others_scripts"> -<TITLE>term 7 2024-03-16 ncurses 6.5 Miscellaneous</TITLE> +<TITLE>term 7 2025-08-16 ncurses 6.6 Miscellaneous</TITLE> <link rel="author" href="mailto:bug-ncurses@gnu.org"> </HEAD> <BODY> -<H1 class="no-header">term 7 2024-03-16 ncurses 6.5 Miscellaneous</H1> +<H1 class="no-header">term 7 2025-08-16 ncurses 6.6 Miscellaneous</H1> <PRE> <STRONG><A HREF="term.7.html">term(7)</A></STRONG> Miscellaneous <STRONG><A HREF="term.7.html">term(7)</A></STRONG> - - </PRE><H2><a name="h2-NAME">NAME</a></H2><PRE> term - conventions for naming terminal types @@ -76,69 +74,69 @@ In any case, you are free to override the system <EM>TERM</EM> setting to your taste in your shell profile. The <STRONG><A HREF="tset.1.html">tset(1)</A></STRONG> utility may be of assistance; - you can give it a set of rules for deducing or requesting a terminal + you can give it a set of rules for deducing or requesting a terminal type based on the tty device and baud rate. - Setting your own <EM>TERM</EM> 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 + Setting your own <EM>TERM</EM> 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. - Terminal type descriptions are stored as files of capability data - underneath /usr/share/terminfo. To browse a list of all terminal names + Terminal type descriptions are stored as files of capability data + underneath <EM>/usr/share/terminfo</EM>. To browse a list of all terminal names recognized by the system, do toe | more 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.1m.html">infocmp(1m)</A></STRONG> + they replace); to examine an entry, you must use the <STRONG><A HREF="infocmp.1m.html">infocmp(1m)</A></STRONG> command. Invoke it as follows: infocmp <EM>entry</EM><STRONG>_</STRONG><EM>name</EM> - where <EM>entry</EM><STRONG>_</STRONG><EM>name</EM> is the name of the type you wish to examine (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 + where <EM>entry</EM><STRONG>_</STRONG><EM>name</EM> is the name of the type you wish to examine (and the + name of its capability file the subdirectory of <EM>/usr/share/terminfo</EM> + 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 "|" (pipe-bar) characters with + 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 "|" (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 <EM>TERM</EM>. The last - name field (if distinct from the first) is actually a description of - the terminal type (it may contain blanks; the others must be single - words). Name fields between the first and last (if present) are + name field (if distinct from the first) is actually a description of + the terminal type (it may contain blanks; the others must be single + words). Name fields between the first and last (if present) are aliases for the terminal, usually historical names retained for compatibility. - There are some conventions for how to choose terminal primary names - that help keep them informative and unique. Here is a step-by-step + There are some conventions for how to choose terminal primary names + that help keep them informative and unique. Here is a step-by-step guide to naming terminals that also explains how to parse them: - First, choose a root name. The root will consist of a lower-case - letter followed by up to seven lower-case letters or digits. You need - to avoid using punctuation characters in root names, because they are + First, choose a root name. The root will consist of a lower-case + letter followed by up to seven lower-case letters or digits. You need + to avoid using punctuation characters in root names, because they are used and interpreted as filenames and shell meta-characters (such as !, $, *, ?, etc.) embedded in them may cause odd and unhelpful behavior. The slash (/), or any other character that may be interpreted by anyone's file system (\, $, [, ]), is especially dangerous (terminfo is - platform-independent, and choosing names with special characters could - someday make life difficult for users of a future port). The dot (.) - character is relatively safe as long as there is at most one per root + platform-independent, and choosing names with special characters could + someday make life difficult for users of a future port). The dot (.) + character is relatively safe as long as there is at most one per root name; some historical terminfo names use it. - The root name for a terminal or workstation console type should almost - always begin with a vendor prefix (such as <STRONG>hp</STRONG> for Hewlett-Packard, <STRONG>wy</STRONG> - for Wyse, or <STRONG>att</STRONG> for AT&T terminals), or a common name of the terminal - line (<STRONG>vt</STRONG> for the VT series of terminals from DEC, or <STRONG>sun</STRONG> for Sun - Microsystems workstation consoles, or <STRONG>regent</STRONG> for the ADDS Regent - series. You can list the terminfo tree to see what prefixes are - already in common use. The root name prefix should be followed when + The root name for a terminal or workstation console type should almost + always begin with a vendor prefix (such as <STRONG>hp</STRONG> for Hewlett-Packard, <STRONG>wy</STRONG> + for Wyse, or <STRONG>att</STRONG> for AT&T terminals), or a common name of the terminal + line (<STRONG>vt</STRONG> for the VT series of terminals from DEC, or <STRONG>sun</STRONG> for Sun + Microsystems workstation consoles, or <STRONG>regent</STRONG> for the ADDS Regent + series. You can list the terminfo tree to see what prefixes are + already in common use. The root name prefix should be followed when appropriate by a model number; 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> be <STRONG>console</STRONG> or any other + 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> be <STRONG>console</STRONG> or any other generic that might cause confusion in a multi-platform environment! If a model number follows, it should indicate either the OS release level or the console driver release level. @@ -161,7 +159,7 @@ -m Mono mode - suppress color support. - -na No arrow keys - termcap ignores arrow keys which are actually + -na No arrow keys - termcap ignores arrow keys which are actually there on the terminal, so the user can use the arrow keys locally. -nam No auto-margin - suppress am capability. @@ -180,13 +178,13 @@ -w Wide; terminal is in 132-column mode. - Conventionally, if your terminal type is a variant 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 + Conventionally, if your terminal type is a variant 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"). - Terminal types that are written not as standalone entries, but rather - as components to be plugged into other entries via <STRONG>use</STRONG> capabilities, + Terminal types that are written not as standalone entries, but rather + as components to be plugged into other entries via <STRONG>use</STRONG> capabilities, are distinguished by using embedded plus signs rather than dashes. Commands which use a terminal type to control display often accept a -T @@ -214,9 +212,7 @@ </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="term.5.html">term(5)</A></STRONG>, <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG> - - -ncurses 6.5 2024-03-16 <STRONG><A HREF="term.7.html">term(7)</A></STRONG> +ncurses 6.6 2025-08-16 <STRONG><A HREF="term.7.html">term(7)</A></STRONG> </PRE> <div class="nav"> <ul> |