2 .\"***************************************************************************
3 .\" Copyright (c) 1998-2016,2017 Free Software Foundation, Inc. *
5 .\" Permission is hereby granted, free of charge, to any person obtaining a *
6 .\" copy of this software and associated documentation files (the *
7 .\" "Software"), to deal in the Software without restriction, including *
8 .\" without limitation the rights to use, copy, modify, merge, publish, *
9 .\" distribute, distribute with modifications, sublicense, and/or sell *
10 .\" copies of the Software, and to permit persons to whom the Software is *
11 .\" furnished to do so, subject to the following conditions: *
13 .\" The above copyright notice and this permission notice shall be included *
14 .\" in all copies or substantial portions of the Software. *
16 .\" THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS *
17 .\" OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF *
18 .\" MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. *
19 .\" IN NO EVENT SHALL THE ABOVE COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, *
20 .\" DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR *
21 .\" OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR *
22 .\" THE USE OR OTHER DEALINGS IN THE SOFTWARE. *
24 .\" Except as contained in this notice, the name(s) of the above copyright *
25 .\" holders shall not be used in advertising or otherwise to promote the *
26 .\" sale, use or other dealings in this Software without prior written *
28 .\"***************************************************************************
30 .\" $Id: tput.1,v 1.50 2017/01/07 23:03:28 tom Exp $
42 \fB@TPUT@\fR, \fBreset\fR \- initialize a terminal or query terminfo database
44 \fB@TPUT@\fR [\fB\-T\fR\fItype\fR] \fIcapname\fR [\fIparameters\fR]
46 \fB@TPUT@\fR [\fB\-T\fR\fItype\fR] \fBclear\fR
48 \fB@TPUT@\fR [\fB\-T\fR\fItype\fR] \fBinit\fR
50 \fB@TPUT@\fR [\fB\-T\fR\fItype\fR] \fBreset\fR
52 \fB@TPUT@\fR [\fB\-T\fR\fItype\fR] \fBlongname\fR
54 \fB@TPUT@ \-S\fR \fB<<\fR
59 The \fB@TPUT@\fR utility uses the \fBterminfo\fR database to make the
60 values of terminal-dependent capabilities and information available to
61 the shell (see \fBsh\fR(1)), to initialize or reset the terminal, or
62 return the long name of the requested terminal type.
63 The result depends upon the capability's type:
67 \fB@TPUT@\fR writes the string to the standard output.
68 No trailing newline is supplied.
71 \fB@TPUT@\fR writes the decimal value to the standard output,
72 with a trailing newline.
75 \fB@TPUT@\fR simply sets the exit code
76 (\fB0\fR for TRUE if the terminal has the capability,
77 \fB1\fR for FALSE if it does not),
78 and writes nothing to the standard output.
81 Before using a value returned on the standard output,
82 the application should test the exit code
83 (e.g., \fB$?\fR, see \fBsh\fR(1)) to be sure it is \fB0\fR.
84 (See the \fBEXIT CODES\fR and \fBDIAGNOSTICS\fR sections.)
85 For a complete list of capabilities
86 and the \fIcapname\fR associated with each, see \fBterminfo\fR(5).
90 indicates the \fItype\fR of terminal.
91 Normally this option is
92 unnecessary, because the default is taken from the environment
94 If \fB\-T\fR is specified, then the shell
95 variables \fBLINES\fR and \fBCOLUMNS\fR will also be ignored.
98 allows more than one capability per invocation of \fB@TPUT@\fR. The
99 capabilities must be passed to \fB@TPUT@\fR from the standard input
100 instead of from the command line (see example).
101 Only one \fIcapname\fR is allowed per line.
102 The \fB\-S\fR option changes the
103 meaning of the \fB0\fR and \fB1\fR boolean and string exit codes (see the
106 Again, \fB@TPUT@\fR uses a table and the presence of parameters in its input
107 to decide whether to use \fBtparm\fR(3X),
108 and how to interpret the parameters.
111 reports the version of ncurses which was used in this program, and exits.
115 indicates the capability from the \fBterminfo\fR database. When
116 \fBtermcap\fR support is compiled in, the \fBtermcap\fR name for
117 the capability is also accepted.
119 If the capability is a string that takes parameters, the arguments
120 following the capability will be used as parameters for the string.
122 Most parameters are numbers.
123 Only a few terminfo capabilities require string parameters;
124 \fB@TPUT@\fR uses a table to decide which to pass as strings.
125 Normally \fB@TPUT@\fR uses \fBtparm\fR(3X) to perform the substitution.
126 If no parameters are given for the capability,
127 \fB@TPUT@\fR writes the string without performing the substitution.
130 If the \fBterminfo\fR database is present and an entry for the user's
131 terminal exists (see \fB\-T\fR\fItype\fR, above), the following will
136 first, \fB@TPUT@\fR retrieves the current terminal mode settings
138 It does this by successively testing
147 ultimately \*(lq/dev/tty\*(rq
150 to obtain terminal settings.
151 Having retrieved these settings, \fB@TPUT@\fP remembers which
152 file descriptor to use when updating settings.
155 if the window size cannot be obtained from the operating system,
156 but the terminal description (or environment, e.g., \fBLINES\fP
157 and \fBCOLUMNS\fP variables specify this),
158 update the operating system's notion of the window size.
161 the terminal modes will be updated:
164 any delays (e.g., newline) specified in the entry will
165 be set in the tty driver,
167 tabs expansion will be turned on or off according to
168 the specification in the entry, and
170 if tabs are not expanded,
171 standard tabs will be set (every 8 spaces).
175 if present, the terminal's initialization strings will be
176 output as detailed in the \fBterminfo\fR(5) section on
177 .IR "Tabs and Initialization" ,
184 contain the information needed for any of these activities,
185 that activity will silently be skipped.
188 This is similar to \fBinit\fP, with two differences:
192 before any other initialization,
193 the terminal modes will be reset to a \*(``sane\*('' state:
196 set cooked and echo modes,
198 turn off cbreak and raw modes,
200 turn on newline translation and
202 reset any unset special characters to their default values
206 Instead of putting out \fIinitialization\fP strings, the terminal's
207 \fIreset\fP strings will be output if present
208 (\fBrs1\fR, \fBrs2\fR, \fBrs3\fR, \fBrf\fR).
209 If the \fIreset\fP strings are not present, but \fIinitialization\fP
210 strings are, the \fIinitialization\fP strings will be output.
213 Otherwise, \fBreset\fR acts identically to \fBinit\fR.
216 If the \fBterminfo\fR database is present and an entry for the
217 user's terminal exists (see \fB\-T\fR\fItype\fR above), then the long name
218 of the terminal will be put out. The long name is the last
219 name in the first line of the terminal's description in the
220 \fBterminfo\fR database [see \fBterm\fR(5)].
222 \fB@TPUT@\fR handles the \fBclear\fP, \fBinit\fP and \fBreset\fP
224 it allows for the possibility that it is invoked by a link with those names.
226 If \fB@TPUT@\fR is invoked by a link named \fBreset\fR, this has the
227 same effect as \fB@TPUT@ reset\fR.
228 The \fB@TSET@\fR(\*n) utility also treats a link named \fBreset\fP specially.
230 Before ncurses 6.1, the two utilities were different from each other:
232 \fB@TSET@\fP utility reset the terminal modes and special characters
233 (not done with \fB@TPUT@\fP).
235 On the other hand, \fB@TSET@\fP's repertoire of terminal capabilities for
236 resetting the terminal was more limited, i.e., only \fBreset_1string\fP, \fBreset_2string\fP and \fBreset_file\fP
237 in contrast to the tab-stops and margins which are set by this utility.
239 The \fBreset\fP program is usually an alias for \fB@TSET@\fP,
240 because of this difference with resetting terminal modes and special characters.
242 With the changes made for ncurses 6.1, the \fIreset\fP feature of the
243 two programs is (mostly) the same. A few differences remain:
245 The \fB@TSET@\fP program waits one second when resetting,
246 in case it happens to be a hardware terminal.
248 The two programs write the terminal initialization strings
249 to different streams (i.e.,. the standard error for \fB@TSET@\fP and the
250 standard output for \fB@TPUT@\fP).
252 \fBNote:\fP although these programs write to different streams,
253 redirecting their output to a file will capture only part of their actions.
254 The changes to the terminal modes are not affected by redirecting the output.
256 If \fB@TPUT@\fR is invoked by a link named \fBinit\fR, this has the
257 same effect as \fB@TPUT@ init\fR.
258 Again, you are less likely to use that link because another program
259 named \fBinit\fP has a more well-established use.
263 Initialize the terminal according to the type of
264 terminal in the environmental variable \fBTERM\fR. This
265 command should be included in everyone's .profile after
266 the environmental variable \fBTERM\fR has been exported, as
267 illustrated on the \fBprofile\fR(5) manual page.
269 \fB@TPUT@ \-T5620 reset\fR
270 Reset an AT&T 5620 terminal, overriding the type of
271 terminal in the environmental variable \fBTERM\fR.
274 Send the sequence to move the cursor to row \fB0\fR, column \fB0\fR
275 (the upper left corner of the screen, usually known as the \*(lqhome\*(rq
279 Echo the clear-screen sequence for the current terminal.
282 Print the number of columns for the current terminal.
284 \fB@TPUT@ \-T450 cols\fR
285 Print the number of columns for the 450 terminal.
287 \fBbold=`@TPUT@ smso` offbold=`@TPUT@ rmso`\fR
288 Set the shell variables \fBbold\fR, to begin stand-out mode
289 sequence, and \fBoffbold\fR, to end standout mode sequence,
290 for the current terminal. This might be followed by a
291 prompt: \fBecho "${bold}Please type in your name: ${offbold}\\c"\fR
294 Set exit code to indicate if the current terminal is a hard copy terminal.
296 \fB@TPUT@ cup 23 4\fR
297 Send the sequence to move the cursor to row 23, column 4.
300 Send the terminfo string for cursor-movement, with no parameters substituted.
302 \fB@TPUT@ longname\fR
303 Print the long name from the \fBterminfo\fR database for the
304 type of terminal specified in the environmental
320 This example shows \fB@TPUT@\fR processing several capabilities in one invocation.
321 It clears the screen,
322 moves the cursor to position 10, 10
323 and turns on bold (extra bright) mode.
324 The list is terminated by an exclamation mark (\fB!\fR) on a line by itself.
328 compiled terminal description database
330 \fB@DATADIR@/tabset/*\fR
331 tab settings for some terminals, in a format
332 appropriate to be output to the terminal (escape
333 sequences that set margins and tabs); for more
335 .IR "Tabs and Initialization" ,
336 section of \fBterminfo\fR(5)
338 If the \fB\-S\fR option is used,
339 \fB@TPUT@\fR checks for errors from each line,
340 and if any errors are found, will set the exit code to 4 plus the
341 number of lines with errors.
342 If no errors are found, the exit code is \fB0\fR.
343 No indication of which line failed can be given so
344 exit code \fB1\fR will never appear. Exit codes \fB2\fR, \fB3\fR, and
345 \fB4\fR retain their usual interpretation.
346 If the \fB\-S\fR option is not used,
347 the exit code depends on the type of \fIcapname\fR:
351 a value of \fB0\fR is set for TRUE and \fB1\fR for FALSE.
354 a value of \fB0\fR is set if the
355 \fIcapname\fR is defined for this terminal \fItype\fR (the value of
356 \fIcapname\fR is returned on standard output);
357 a value of \fB1\fR is set if \fIcapname\fR
358 is not defined for this terminal \fItype\fR
359 (nothing is written to standard output).
362 a value of \fB0\fR is always set,
363 whether or not \fIcapname\fR is defined for this terminal \fItype\fR.
364 To determine if \fIcapname\fR is defined for this terminal \fItype\fR,
365 the user must test the value written to standard output.
367 means that \fIcapname\fR is not defined for this terminal \fItype\fR.
370 \fBreset\fR or \fBinit\fR may fail to find their respective files.
371 In that case, the exit code is set to 4 + \fBerrno\fR.
374 Any other exit code indicates an error; see the DIAGNOSTICS section.
376 \fB@TPUT@\fR prints the following error messages and sets the corresponding exit
382 exit code error message
385 (\fIcapname\fR is a numeric variable that is not specified in the
386 \fBterminfo\fR(5) database for this terminal type, e.g.
387 \fB@TPUT@ \-T450 lines\fR and \fB@TPUT@ \-T2621 xmc\fR)
389 \fB1\fR no error message is printed, see the \fBEXIT CODES\fR section.
391 \fB3\fR unknown terminal \fItype\fR or no \fBterminfo\fR database
392 \fB4\fR unknown \fBterminfo\fR capability \fIcapname\fR
393 \fB>4\fR error occurred in \-S
397 The \fBtput\fP command was begun by Bill Joy in 1980.
398 The initial version only cleared the screen.
400 AT&T System V provided a different \fBtput\fP command,
401 whose \fBinit\fP and \fBreset\fP subcommands
402 (more than half the program) were incorporated from
403 the \fBreset\fP feature of BSD \fBtset\fP written by Eric Allman.
404 Later the corresponding source code for \fIreset\fP
405 was removed from the BSD \fBtset\fP
406 (in June 1993, released in 4.4BSD-Lite a year later).
408 Keith Bostic replaced the BSD \fBtput\fP command in 1989 with a new implementation
409 based on the AT&T System V program \fBtput\fP.
410 Like the AT&T program, Bostic's version
411 accepted some parameters named for \fIterminfo capabilities\fP
412 (\fBclear\fP, \fBinit\fP, \fBlongname\fP and \fBreset\fP).
413 However (because he had only termcap available),
414 it accepted \fItermcap names\fP for other capabilities.
415 Also, Bostic's BSD \fBtput\fP did not modify the terminal I/O modes
416 as the earlier BSD \fBtset\fP had done.
418 At the same time, Bostic added a shell script named \*(lqclear\*(rq,
419 which used \fBtput\fP to clear the screen.
421 Both of these appeared in 4.4BSD,
422 becoming the \*(lqmodern\*(rq BSD implementation of \fBtput\fP.
425 This implementation of \fBtput\fP differs from AT&T \fBtput\fP in
428 \fB@TPUT@\fP \fIcapname\fP writes to the standard output.
429 That need not be a regular terminal.
430 However, the subcommands which manipulate terminal modes
431 may not use the standard output.
433 The AT&T implementation's \fBinit\fP and \fBreset\fP commands
434 use the BSD (4.1c) \fBtset\fP source, which manipulates terminal modes.
435 It successively tries standard output, standard error, standard input
436 before falling back to \*(lq/dev/tty\*(rq and finally just assumes
438 When updating terminal modes, it ignores errors.
440 Until changes made after ncurses 6.0, \fB@TPUT@\fP did not modify terminal modes.
441 \fB@TPUT@\fP now uses a similar scheme,
442 using functions shared with \fB@TSET@\fP
443 (and ultimately based on the 4.4BSD \fBtset\fP).
444 If it is not able to open a terminal, e.g., when running in \fBcron\fP,
445 \fB@TPUT@\fP will return an error.
447 AT&T \fBtput\fP guesses the type of its \fIcapname\fP operands by seeing if
448 all of the characters are numeric, or not.
450 Most implementations which provide support for \fIcapname\fR operands
451 use the \fItparm\fP function to expand parameters in it.
452 That function expects a mixture of numeric and string parameters,
453 requiring \fB@TPUT@\fP to know which type to use.
455 This implementation uses a table to determine the parameter types for
456 the standard \fIcapname\fR operands, and an internal library
457 function to analyze nonstandard \fIcapname\fR operands.
459 The \fBlongname\fR and \fB\-S\fR options, and the parameter-substitution
460 features used in the \fBcup\fR example,
461 were not supported in BSD curses before 4.3reno (1989) or in
462 AT&T/USL curses before SVr4 (1988).
464 IEEE Std 1003.1/The Open Group Base Specifications Issue 7 (POSIX.1-2008)
465 documents only the operands for \fBclear\fP, \fBinit\fP and \fBreset\fP.
466 There are a few interesting observations to make regarding that:
468 In this implementation, \fBclear\fP is part of the \fIcapname\fR support.
469 The others (\fBinit\fP and \fBlongname\fP) do not correspond to terminal
472 Other implementations of \fBtput\fP on
473 SVr4-based systems such as Solaris, IRIX64 and HPUX
474 as well as others such as AIX and Tru64
475 provide support for \fIcapname\fR operands.
477 A few platforms such as FreeBSD recognize termcap names rather
478 than terminfo capability names in their respective \fBtput\fP commands.
479 Since 2010, NetBSD's \fBtput\fP uses terminfo names.
480 Before that, it (like FreeBSD) recognized termcap names.
482 Because (apparently) \fIall\fP of the certified Unix systems
483 support the full set of capability names, the reasoning for documenting
484 only a few may not be apparent.
486 X/Open Curses Issue 7 documents \fBtput\fP differently, with \fIcapname\fP
487 and the other features used in this implementation.
489 That is, there are two standards for \fBtput\fP: POSIX (a subset) and X/Open Curses (the full implementation).
490 POSIX documents a subset to avoid the complication of including X/Open Curses
491 and the terminal capabilities database.
493 While it is certainly possible to write a \fBtput\fP program without using curses,
494 none of the systems which have a curses implementation provide
495 a \fBtput\fP utility which does not provide the \fIcapname\fP feature.
502 \fBcurs_termcap\fR(3X).
504 This describes \fBncurses\fR
505 version @NCURSES_MAJOR@.@NCURSES_MINOR@ (patch @NCURSES_PATCH@).
projects / ncurses.git / blob