NAME

type - write a description of command type

 SYNOPSIS

type name...

 DESCRIPTION

The type utility indicates how each argument would be interpreted if used as a command name.

 OPTIONS

None.

 OPERANDS

The following operand is supported:

name

A name to be interpreted.

 STDIN

Not used.

 INPUT FILES

None.

 ENVIRONMENT VARIABLES

The following environment variables affect the execution of type:

LANG

Provide a default value for the internationalisation variables that are unset or null. If LANG is unset or null, the corresponding value from the implementation-dependent default locale will be used. If any of the internationalisation variables contains an invalid setting, the utility will behave as if none of the variables had been defined.

LC_ALL

If set to a non-empty string value, override the values of all the other internationalisation variables.

LC_CTYPE

Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single- as opposed to multi-byte characters in arguments).

LC_MESSAGES

Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error.

NLSPATH

Determine the location of message catalogues for the processing of LC_MESSAGES .

PATH

Determine the location of name, as described in the XBD specification, Environment Variables  .

 ASYNCHRONOUS EVENTS

Default.

 STDOUT

The standard output of type contains information about each operand in an unspecified format. The information provided typically identifies the operand as a shell built-in, function, alias or keyword, and where applicable, may display the operand's pathname.

 STDERR

Used only for diagnostic messages.

 OUTPUT FILES

None.

 EXTENDED DESCRIPTION

None.

 EXIT STATUS

The following exit values are returned:

0

Successful completion.

>0

An error occurred.

 CONSEQUENCES OF ERRORS

Default.

 APPLICATION USAGE

Since type must be aware of the contents of the current shell execution environment (such as the lists of commands, functions and built-ins processed by hash), it is always provided as a shell regular built-in. If it is called in a separate utility execution environment, such as one of the following:

nohup type writer
find . -type f | xargs type

it might not produce accurate results.

 EXAMPLES

None.

 FUTURE DIRECTIONS

None.

 SEE ALSO

command.