NAME

tabs − set tabs on a terminal

SYNOPSIS

tabs [ tabspec ] [ −Ttype ] [ +mn ]

AVAILABILITY

SUNWcsu

DESCRIPTION

tabs sets the tab stops on the user’s terminal according to the tab specification tabspec, after clearing any previous settings. The user’s terminal must have remotely settable hardware tabs.

OPTIONS

tabspec Four types of tab specification are accepted for tabspec. They are described below: canned (−code), repetitive (−n), arbitrary (n1,n2,...), and file (−−file).  If no tabspec is given, the default value is −8, that is, UNIX system “standard” tabs.  The lowest column number is 1.  Note:  For tabs, column 1 always refers to the leftmost column on a terminal, even one whose column markers begin at 0, for example, the DASI 300, DASI 300s, and DASI 450. 

−code Use one of the codes listed below to select a canned set of tabs.  The legal codes and their meanings are as follows:

−a 1,10,16,36,72
Assembler, IBM S/370, first format

−a2 1,10,16,40,72
Assembler, IBM S/370, second format

−c 1,8,12,16,20,55
COBOL, normal format

−c2 1,6,10,14,49
COBOL compact format (columns 1-6 omitted).  Using this code, the first typed character corresponds to card column 7, one space gets you to column 8, and a tab reaches column 12.  Files using this tab setup should include a format specification as follows (see fspec(4) ):

<:t−c2 m6 s66 d:>

−c3 1,6,10,14,18,22,26,30,34,38,42,46,50,54,58,62,67
COBOL compact format (columns 1-6 omitted), with more tabs than −c2. This is the recommended format for COBOL.  The appropriate format specification is (see fspec(4)):

<:t−c3 m6 s66 d:>

−f 1,7,11,15,19,23
FORTRAN

−p 1,5,9,13,17,21,25,29,33,37,41,45,49,53,57,61
PL/I

−s 1,10,55
SNOBOL

−u 1,12,20,44
UNIVAC 1100 Assembler

−n A repetitive specification requests tabs at columns 1+n, 1+2∗n, etc. Of particular importance is the value 8: this represents the UNIX system “standard” tab setting, and is the most likely tab setting to be found at a terminal.  Another special case is the value 0, implying no tabs at all. 

n1,n2,... The arbitrary format permits the user to type any chosen set of numbers, separated by commas, in ascending order.  Up to 40 numbers are allowed.  If any number (except the first one) is preceded by a plus sign, it is taken as an increment to be added to the previous value.  Thus, the formats 1,10,20,30, and 1,10,+10,+10 are considered identical. 

−−file If the name of a file is given, tabs reads the first line of the file, searching for a format specification (see fspec(4)).  If it finds one there, it sets the tab stops according to it, otherwise it sets them as −8.  This type of specification may be used to make sure that a tabbed file is printed with correct tab settings, and would be used with the pr command:

example% tabs −− file; pr file

Any of the following also may be used; if a given flag occurs more than once, the last value given takes effect:

−Ttype tabs usually needs to know the type of terminal in order to set tabs and always needs to know the type to set margins.  type is a name listed in term(5).  If no −T flag is supplied, tabs uses the value of the environment variable TERM.  If TERM is not defined in the environment (see environ(5)), tabs tries a sequence that will work for many terminals. 

+mn The margin argument may be used for some terminals.  It causes all tabs to be moved over n columns by making column n+1 the left margin.  If +m is given without a value of n, the value assumed is 10.  For a TermiNet, the first value in the tab list should be 1, or the margin will move even further to the right.  The normal (leftmost) margin on most terminals is obtained by +m0.  The margin for most terminals is reset only when the +m flag is given explicitly. 

Tab and margin setting is performed via the standard output. 

EXAMPLES

The command:

example% tabs −a

is an example using −code (canned specification) to set tabs to the settings required by the IBM assembler:  columns 1, 10, 16, 36, 72. 

The next command:

example% tabs −8

is an example of using −n (repetitive specification), where n is 8, causes tabs to be set every eighth position:
1+(1∗8), 1+(2∗8), ... which evaluate to columns 9, 17, ...

The command:

example% tabs 1,8,36

is an example of using n1,n2,... (arbitrary specification) to set tabs at columns 1, 8, and 36. 

The last command:

example% tabs −−$HOME/fspec.list/att4425

is an example of using −−file (file specification) to indicate that tabs should be set according to the first line of $HOME/fspec.list/att4425 (see fspec(4)). 

ENVIRONMENT

If any of the LC_∗ variables ( LC_CTYPE, LC_MESSAGES, LC_TIME, LC_COLLATE, LC_NUMERIC, and LC_MONETARY ) (see environ(5)) are not set in the environment, the operational behavior of tabs for each corresponding locale category is determined by the value of the LANG environment variable.  If LC_ALL is set, its contents are used to override both the LANG and the other LC_∗ variables.  If none of the above variables is set in the environment, the "C"  (U.S. style) locale determines how tabs behaves. 

LC_CTYPE
Determines how tabs handles characters. When LC_CTYPE is set to a valid value, tabs can display and handle text and filenames containing valid characters for that locale.  tabs can display and handle Extended Unix Code (EUC) characters where any individual character can be 1, 2, or 3 bytes wide.  tabs can also handle EUC characters of 1, 2, or more column widths. In the "C" locale, only characters from ISO 8859-1 are valid. 

LC_MESSAGES
Determines how diagnostic and informative messages are presented. This includes the language and style of the messages, and the correct form of affirmative and negative responses.  In the "C" locale, the messages are presented in the default form found in the program itself (in most cases, U.S. English).

SEE ALSO

newform(1), pr(1), tput(1), fspec(4), terminfo(4), environ(5), term(5)

DIAGNOSTICS

illegal tabs This occurs when arbitrary tabs are ordered incorrectly. 

illegal increment This occurs when a zero or missing increment is found in an arbitrary specification. 

unknown tab code This occurs when a canned code cannot be found. 

can’t open The −−file option was used, and file cannot be opened. 

file indirection The −−file option was used and the specification in that file points to yet another file.  Indirection of this form is not permitted. 

NOTES

There is no consistency among different terminals regarding ways of clearing tabs and setting the left margin. 

tabs clears only 20 tabs (on terminals requiring a long sequence), but is willing to set 64. 

The tabspec used with the tabs command is different from the one used with the newform command.  For example, tabs −8 sets every eighth position; whereas newform −i−8 indicates that tabs are set every eighth position. 

Sun Microsystems  —  Last change: 14 Sep 1992