Cat (Unix)

Article in other languages:

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

Contents

Specification

The Single Unix Specification specifies the behavior that the contents of each of the files given in sequence as arguments will be written 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 entered.

Extensions

Both the BSD versions of cat (as per the OpenBSD manpage) and the GNU coreutils version of cat specify 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.4.7 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 critics, 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.

Useless use of cat

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

Without two named files cat is a useless use of cat. A UUOC campaign will eliminate the inefficiency from shell scripts by using redirection instead. But cat with one named file is safer where human error is a concern— one wrong use of the default [1] redirection symbol ">" instead of "<" (often adjacent on keyboards) will permanently delete [2] the file you were just needing to read.

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[3].

Other operating systems

The equivalent command in the VMS, CP/M, DOS, OS/2, and Microsoft Windows operating system command shells is type.

See also

External links

Manual pages

Other

References

  1. ^ The default behavior for redirection is to clobber the file to it's immediate right.
  2. ^ More accurately stated ">" will truncate the file.
  3. ^ A moggy is British-influenced word for cat.

Questions for article:

This article is from Wikipedia. All text is available under the terms of the GNU Free Documentation License.


IHS Europe: Infrared Heating Systems for Home and Business.