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
file to standard output than to concatenate two files. The name
`cat' for the former operation is just as unintuitive as, say,
LISP's {cdr}.

Of such oppositions are {holy wars} made....

:catatonic: /adj./ Describes a condition of suspended animation
in which something is so {wedged} or {hung} that it makes no
response. If you are typing on a terminal and suddenly the
computer doesn't even echo the letters back to the screen as you
type, let alone do what you're asking it to do, then the computer
is suffering from catatonia (possibly because it has crashed).
"There I was in the middle of a winning game of {nethack} and
it went catatonic on me! Aaargh!" Compare {buzz}.

:cd tilde: /C-D til-d*/ /vi./ To go home. From the Unix
C-shell and Korn-shell command `cd ~', which takes one to
one's `$HOME' (`cd' with no arguments happens to do the