cat (Unix)

This article is about the Unix command. For the animal, see Cat. For other uses, see Cat (disambiguation).

The cat (from catenate, a synonym of concatenate) command is a standard Unix program used to concatenate and display files.

Specification

The Single Unix Specification specifies the behaviour that each of the files given in sequence as arguments will write their contents to the standard output in the same sequence, and mandates one option, -u, where each byte is printed as it is read.

If the filename is specified as -, then cat will read from standard input at that point in the sequence. If no files are specified, cat will read from standard input.

Extensions

Both BSD versions of cat (as per the OpenBSD) manpage and the GNU coreutils version of cat specifies the following options:

• -b (GNU only: --number-nonblank), number non-blank output lines
• -n (GNU only: --number), number all output lines
• -s (GNU only: --squeeze-blank), squeeze multiple adjacent blank lines
• -v (GNU only: --show-nonprinting), displays nonprinting characters as if they were visible, except for tabs and the end of line character
• -t on BSD, -T on GNU, implies -v but also display tabs as ^I
• -e on BSD, -E on GNU, implies -v but also display end-of-line characters as $

Unix culture

Jargon File definition

The Jargon File version 4.3.3 lists this as the definition of cat:

1. To spew an entire file to the screen or some other output sink without pause (syn. blast). 2. By extension, to dump large amounts of data at an unprepared target or with no intention of browsing it carefully. Usage: considered silly. Rare outside Unix sites. See also dd, BLT.

Among Unix fans, cat(1) is considered an excellent example of user-interface design, because it delivers the file contents without such verbosity as spacing or headers between the files, and because it does not require the files to consist of lines of text, but works with any sort of data.

Among Unix haters, cat(1) is considered the canonical example of bad user-interface design, because of its woefully unobvious name. It is far more often used to blast a single file to standard output than to concatenate two or more files. The name cat for the former operation is just as unintuitive as, say, LISP's cdr.

cat and UUOC

UUOC (from comp.unix.shell on Usenet) stands for "Useless Use of cat". As received wisdom on comp.unix.shell observes, "The purpose of cat is to concatenate (or 'catenate') files. If it's only one file, concatenating it with nothing at all is a waste of time, and costs you a process." Nevertheless one sees people doing

cat file | some_command and its args ...

instead of the equivalent and cheaper

<file some_command and its args ...

or (equivalently and more classically)

some_command and its args ... <file

Since 1995, occasional awards for UUOC have been given out, usually by Perl luminary Randal L. Schwartz. There is a web page devoted to this and other similar awards. In British hackerdom the activity of fixing instances of UUOC is sometimes called demoggification.

See also

• Coreutils
• List of Unix programs
• split — splits a file into pieces which cat can then rejoin

External links

• cat -- specification from the Single Unix Specification

Manual pages

• cat -- manual page from GNU coreutils
• cat -- manual page from OpenBSD

Other

• UUOC awards