Lines Matching full:terminal

51 initialize a terminal, exercise its capabilities, or query \fI\%term\%info\fP database
53 \fB@TPUT@\fP [\fB\-T\fP \fIterminal-type\fP]
56 \fB@TPUT@\fP [\fB\-T\fP \fIterminal-type\fP] [\fB\-x\fP] \fBclear\fP
58 \fB@TPUT@\fP [\fB\-T\fP \fIterminal-type\fP] \fBinit\fP
60 \fB@TPUT@\fP [\fB\-T\fP \fIterminal-type\fP] \fB\%reset\fP
62 \fB@TPUT@\fP [\fB\-T\fP \fIterminal-type\fP] \fB\%longname\fP
70 library and database to make terminal-specific capabilities and
72 to initialize or reset the terminal,
76 terminal type.
77 Terminal capabilities are accessed by
80 \fB\%terminfo\fP(5) discusses terminal capabilities at length
90 if the terminal possesses
118 a capability code from the terminal database,
130 indicates a capability from the terminal database.
141 Only a few terminal capabilities require string parameters;
149 initializes the terminal.
150 If the terminal database is present
151 and an entry for the user's terminal type exists,
156 \fB\%@TPUT@\fP retrieves the terminal's mode settings.
170 to obtain terminal settings.
175 If the terminal dimensions cannot be obtained from the operating system,
176 but the environment or terminal type database entry describes them,
180 \fB\%@TPUT@\fP updates the terminal modes.
186 are set in the terminal driver.
212 re-initializes the terminal.
217 \fB\%@TPUT@\fP sets the the terminal modes to a \*(``sane\*('' state,
231 If any reset capabilities are defined for the terminal type,
244 before the list of terminal capabilities.
255 If the terminal database is present and an entry for the user's terminal
267 Changes to the terminal modes are not affected by file descriptor
269 since the terminal modes are altered via \fB\%ioctl\fP(2).
300 .SS "Terminal Size"
310 it may call \fB\%setupterm\fP(3X) to obtain the terminal size.
313 \fB\%@TPUT@\fP attempts to obtain these capabilities from the terminal
315 This generally fails for terminal emulators,
318 It then asks the operating system for the terminal's size,
328 which may override the terminal size.
338 the terminal database).
364 indicates the terminal's
400 2	usage error or no terminal type specified
401 3	unrecognized terminal type
426 denotes the terminal type.
427 Each terminal type is distinct,
438 compiled terminal description database
449 which need not be a terminal device.
451 the operands that manipulate terminal modes might not use the standard
461 manipulating terminal modes.
465 for association with a terminal device as
469 finally assumes a 1200 baud terminal.
470 When updating terminal modes,
477 \fB\%@TPUT@\fP did not modify terminal modes.
482 If it is not able to open a terminal
636 do not correspond to terminal capabilities.
696 X/Open Curses and the terminal capability database.
817 did not modify the terminal modes as the earlier BSD
838 Ridge's program made more sophisticated use of the terminal capabilities
848 Incorporating the portions dealing with terminal capabilities
859 resetting the terminal modes and special characters.
862 \fB\%@TSET@\fP's repertoire of terminal capabilities for resetting the
863 terminal was more limited;
877 to reset terminal modes and special characters.
886 in case the terminal happens to be a hardware device.
888 The two programs write the terminal initialization strings
896 Initialize the terminal according to the type of
897 terminal in the
900 If the system does not reliably initialize the terminal upon login,
908 Reset an AT&T 5620 terminal,
909 overriding the terminal type in the
929 Report the number of columns used by the current terminal type.
932 Report the number of columns used by an ADM-3A terminal.
941 stand-out mode for the terminal.
951 Indicate via exit status whether the terminal is a hard copy device.
968 database's description of the terminal type specified in the