type - write a description of command type
[XSI] type name...
The type utility shall indicate how each argument would be interpreted if used as a command name.
The following operand shall be supported:
- A name to be interpreted.
The following environment variables shall affect the execution of type:
- Provide a default value for the internationalization variables that are unset or null. (See XBD Internationalization Variables for the precedence of internationalization variables used to determine the values of locale categories.)
- If set to a non-empty string value, override the values of all the other internationalization variables.
- Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multi-byte characters in arguments).
- Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error.
- Determine the location of message catalogs for the processing of LC_MESSAGES.
- Determine the location of name, as described in XBD Environment Variables.
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.
The standard error shall be used only for diagnostic messages.
The following exit values shall be returned:
- Successful completion.
- An error occurred.
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 typeit might not produce accurate results.
XBD Environment Variables
First released in Issue 2.
return to top of page