Is there ever a reason to use `cat` when you've got `less`?

Although both commands allow you to view the content of a file, their original purposes are quite different.

less extends the capabilities of more. The latter was created to view the content of a file one screenful at a time. less adds features such as backward movements and better memory management (no need to read the entire file before being able to see the first lines).

cat concatenates files and prints the result on the standard output. If you provide only one file, you will see the content of that file. It becomes 'powerful' when you provide multiple files. A good example is the combination of split and cat. The first command will divide a large file in small portions. The second one will then concatenate the small portions into a single file.

Back to your question, cat would be preferred in an autonomous script requiring files to be read entirely (or concatenated) without interaction. In terms of file viewing, I think it's more a question of taste.

I usually use cat when I need to type a command based on something in the file. cat is more convenient since you can see the file (if it's small) while you have access to the shell prompt. It also allows for pipe lining.

There are people who argue violently that the only purpose of cat is to concatenate files. For every other use, there is more (or less).

But this fails to take into account one quite important fact: cat is one character less to type. I use those commands so often that one character less is a no-brainer.

Another reason is when you want to create a file. I often copy-and-paste text from the web into a file like this (command prompt shown):

$ cat > filename <Cmd-V> <Ctrl-D> $ 

That is, I open a file filename for write access, paste the content and close the stream by pressing Ctrl-D. Neither less nor more can do that, and it’s faster than opening an editor.

Is there any situation where cat is a better solution?

When you are dealing with more that one file and wish to concatenate them.

From the man page:

cat f - g Output f's contents, then standard input, then g's contents.

Sometimes you don't want the pagination that less does and just want the complete file so you'd use cat.

I use cat to grep (multiple) files.

cat <filename1> [<filename2> <filename3>] | grep -i "string of interest"

I know grep supports filenames, but If you are grepping the same file for different search terms, editing a command where the search term is the last thing on the line is easier then having to ctrl+arrow-key back through the line.

cat can be used to concat several binary files into one big one:

cat data.001 data.002 data.003 > bigdata.dat 

I use less -FX, which makes less behave like cat when a file can be displayed on one screen. From the less(1) manpage:

-F or --quit-if-one-screen Causes less to automatically exit if the entire file can be dis- played on the first screen. -X or --no-init Disables sending the termcap initialization and deinitialization strings to the terminal. This is sometimes desirable if the deinitialization string does something unnecessary, like clear- ing the screen. 

The cat stays on the screen. Everything less disapears.

Clarified by/for Volker Siegel:

The output of cat stays on the screen. Everything shown by less disapears after closing.

I guess, because of the poularity of Unix variants now, many people don't have to administer their systems (with a vengence). When things go tits-up you might just be able to reboot and enter your system in what is called a restricted environment.

You get a command line and access to a small set of what is deemed useful commands that are small and usually statically linked. You might get vi as an editor or even the smaller ed, but not emacs or vim. You would get cat, but not less. The idea is to give you enough tools to repair your system without taking too much resources as those resources may be incorrectly configured, or all used up. the less command onder those circumstances is superfluous.

And less is not pre-installed on all GNU/Linux distributions. (eg. Gentoo) cat is everywhere, probably.

There can be an issue with privilege escalation, as within 'less' you can press 'v' to edit a file or '!' to send a shell command.

You might want to allow some users to view a file that can only be read by the superuser, but not allow those users to edit the file or to use superuser privileges in general. You could do this by editing '/etc/sudoers' to allow them to use 'sudo /bin/cat /etc/importantfile'. You wouldn't want to allow 'sudo /usr/bin/less /etc/importantfile', because they could use 'v' to edit the file, or use '!' to launch a shell with full superuser privileges.

Of course, the users could use 'sudo /bin/cat /etc/importantfile | less' and still use 'less', without the security risks.

For convenience. cat have 3 characters while more/less have 4 characters. And typing cat only require your left hand only.

The two are different. less is a non-standard pager (more is the standard one), used for viewing text a screenful at a time, while cat is a standard utility, used for concatenating any type and number of data streams into one, non-interactively.

They may appear to do the same thing under certain circumstances, but so do other utilities.

In terms of how to show the characters on the screen, less can do what cat can do; And much more.

But there is a very good reason to use cat for some cases:
less is just too complex to throw it on very simple problems. I has so many options that it's hard to find the cat-related ones in the man page.

Want to show the tabs in a Makefile?

In man cat, the first option is -A.
The description is not helpful: -vET.
But the long option name sounds just right: --show-all.

And cat -A Makefile does what I need.

Now, go find that for less.

Both 'less' and 'more' will work exactly like 'cat' if the output is not a terminal (tty), as to pipes and files, they will both revert to no pagination.

I think it's safe to say that 'cat' is always present on any Unix-type system you will ever find. The presence of 'less' and/or 'more' on any system is less predictable.

In scripts therefore, if you need only a non-pagination operation, 'cat' is sure to be present wherever your script is used on a Unix-type system.

cat works better when displaying color ASCII art, which can be important to consider when reviewing logged terminal output:

#!/bin/bash # log all terminal output exec &> >(tee -a log.txt) # ANSII color codes color_blue=$(tput setaf 4) color_reset=$(tput sgr0) bold=$(tput bold) # display banner printf '%s' "${color_blue}${bold}" cat <<'EOF' ::::::::: :::::::::: ::::::::: ::: :::::::: ::: ::: :+: :+: :+: :+: :+: :+: :+: :+: :+: :+: +:+ +:+ +:+ +:+ +:+ +:+ +:+ +:+ +:+ +:+ +#+ +:+ +#++:++# +#++:++#+ +#+ +#+ +:+ +#++: +#+ +#+ +#+ +#+ +#+ +#+ +#+ +#+ #+# #+# #+# #+# #+# #+# #+# #+# ######### ########## ### ########## ######## ### EOF printf '%s' "${color_reset}" 

Displays log with full color:

cat log.txt 

Color is glitched after first line:

less log.txt less -r log.txt 

less will also mangle the display terribly while paging back-and-forth if you've got ANSII control characters in the file, which can occur when logging interactive scripts which use techniques like this.