tac (Unix)

cat is a standard Unix utility that reads files sequentially, writing them to standard output. The name is derived from its function to (con)catenate files (from Latin ''catenare'', "to chain"). It has been ported to a number of operating systems.

History

cat was part of the early versions of Unix, e.g., Version 1, and replaced pr, a PDP-7 and Multics utility for copying a single file to the screen. It was written by Ken Thompson and Dennis Ritchie.
The version of cat bundled in GNU coreutils was written by Torbjorn Granlund and Richard Stallman. The ReactOS version was written by David Welch, Semyon Novikov, and Hermès Bélusca.

Over time, alternative utilities such as tac and bat also became available, bringing different new features.

Usage

The Single Unix Specification defines the operation of cat to read files in the sequence given in its arguments, writing their contents to the standard output in the same sequence. The specification mandates the support of one option flag, ''u'' for unbuffered output, meaning that each byte is written after it has been read. Some operating systems, like the ones using GNU Core Utilities, do this by default and ignore the flag.GNU Coreutils
"GNU Coreutils manual"
''GNU'', Retrieved on 1 Mars 2017.

If one of the input filenames is specified as a single hyphen (''-''), then cat reads from standard input at that point in the sequence. If no files are specified, cat reads from standard input only.

The command- syntax is:
cat ptions ile_names

Options

Example of some cat options:

* (GNU: ), number non-blank output lines
* implies but also display end-of-line characters as (GNU only: the same, but without implying )
* (GNU: ), number all output lines
* (GNU: ), squeeze multiple adjacent blank lines
* implies , but also display tabs as (GNU: the same, but without implying )
* use unbuffered I/O for stdout. POSIX does not specify the behavior without this option.
* (GNU: ), displays nonprinting characters, except for tabs and the end of line character

Use cases

cat can be used to pipe a file to a program that expects plain text or binary data on its input stream. cat does not destroy non-text bytes when concatenating and outputting. As such, its two main use cases are text files and certain format-compatible types of binary files.

Concatenation of text is limited to text files using the same legacy encoding, such as ASCII. cat does not provide a way to concatenate Unicode text files that have a Byte Order Mark or files using different text encodings from each other.

For many structured binary data sets, the resulting combined file may not be valid; for example, if a file has a unique header or footer, the result will spuriously duplicate these. However, for some multimedia digital container formats, the resulting file is valid, and so cat provides an effective means of appending files. Video streams can be a significant example of files that cat can concatenate without issue, e.g. the MPEG program stream (MPEG-1 and MPEG-2) and DV (Digital Video) formats, which are fundamentally simple streams of packets.

Examples

Unix culture

Jargon file definition

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

Useless use of cat

''Useless use of cat'' (''UUOC'') is common Unix jargon for command line constructs that only provide a function of convenience to the user.comp.unix.shell
"Early award example of UUOC (1994)"
'' comp.unix.shell via Google Groups'', Retrieved on 1 Mars 2017. In computing, the word "abuse", in the second sense of the definition, is used to disparage the excessive or unnecessary use of a language construct; thus, abuse of cat is sometimes called "cat abuse". Example of a common cat abuse is given in the award:
cat filename , command arg1 arg2 argn

This can be rewritten using redirection of stdin instead, in either of the following forms (the first is more traditional):

 command arg1 arg2 argn < filename
 
Beyond other benefits, the input redirection forms allow ''command'' to perform  random access on the file, whereas the cat examples do not. This is because the redirection form opens the file as the stdin file descriptor which ''command'' can fully access, while the cat form simply provides the data as a stream of bytes.
Another common case where cat is unnecessary is where a command defaults to operating on stdin, but will read from a file, if the filename is given as an argument. This is the case for many common commands; the following examples
 cat file ,  grep pattern
 cat file ,  less

can instead be written as
 grep pattern file
 less file
A common interactive use of cat for a single file is to output the content of a file to standard output. However, if the output is piped or redirected, cat is unnecessary.
A cat written with UUOC might still be preferred for readability reasons, as reading a piped stream left-to-right might be easier to conceptualize. Also, one wrong use of the redirection symbol ">" instead of "<" (often adjacent on keyboards) may permanently delete the content of a file, in other words clobbering, and one way to avoid this is to use cat with pipes. Compare:
 command < in ,  command2 > out
  out

with:
 cat in ,  command ,  command2 > out

 See also

*  paste
* split, a command that splits a file into pieces which cat can then rejoin.
*  zcat
* less

 References

 External links
* 

UNIX Style, or cat -v Considered Harmful
- A paper by Rob Pike on proper Unix command design using cat as an example.

cat(1) original manual page
in the First Edition of Unix.
* 
* 
* 
* 
* 
{{Core Utilities commands
 Unix text processing utilities
Cat
 Unix SUS2008 utilities
 IBM i Qshell commands