{"id":4027,"date":"2018-05-22T17:17:51","date_gmt":"2018-05-22T13:17:51","guid":{"rendered":"https:\/\/www.howtoforge.com\/linux-tac-command\/"},"modified":"2018-05-22T17:17:51","modified_gmt":"2018-05-22T13:17:51","slug":"linux-tac-command-tutorial-for-beginners-with-examples","status":"publish","type":"post","link":"https:\/\/afaghhosting.net\/blog\/linux-tac-command-tutorial-for-beginners-with-examples\/","title":{"rendered":"Linux tac Command Tutorial for Beginners (with Examples)"},"content":{"rendered":"

We’ve already discussed the Linux cat command<\/a>\u00a0in one of our earlier tutorials. As you may be aware, the cat command is mainly used for displaying file contents in output. However, what you may not be aware of is that there exists a command that does exactly opposite of what cat does.<\/p>\n

The tool in question is tac<\/strong>, and in this tutorial, we will discuss its basics using some easy to understand examples. But before we do that, it’s worth mentioning that all examples in this article have been tested on an Ubuntu 16.04 LTS machine.<\/p>\n

Linux tac command<\/h2>\n

Tac is opposite to cat in the sense that the output it produces is presented in a way that the last line is displayed first, then the second last line, and so on. Following is the tool’s syntax:<\/p>\n

tac [OPTION]… [FILE]…<\/p>\n

And here’s what tac’s man page says about it:<\/p>\n

Write each FILE to standard output, last line first. With no FILE, or when FILE is -, read standard input.<\/pre>\n
Following are some Q&A-styled examples that should give you a good idea on how the tool works.<\/p>\n
Q1. How to use tac?<\/h2>\n
Simple, just run the ‘tac’ command with a filename as input.<\/p>\n
tac [filename]<\/p>\n
For example:<\/p>\n
tac file2<\/p>\n
\"How<\/a><\/p>\n
So you can see the output produced by tac is exactly opposite of what cat produced.<\/p>\n
Q2. How to make tac use custom separator (not newline)?<\/h2>\n
For this, you’ll have to use the -s option. For example, the following command<\/p>\n
echo “1,2” | tac<\/p>\n
Produced this output:<\/p>\n
1,2<\/pre>\n
That’s because newline is the default separator for tac.<\/p>\n
However, the command below:<\/p>\n
echo “1,2” | tac -s ,<\/p>\n
produces the following output:<\/p>\n
21,<\/pre>\n
That’s because now the separator has been changed.<\/p>\n
Q3. How to change the position of separator?<\/h2>\n
If you want tac to attach the separator before instead of after, use the -b option.<\/p>\n
For example:<\/p>\n
echo “1,2” | tac -b -s ,<\/p>\n
produces the following output:<\/p>\n
,21<\/pre>\n
Q4. How to make tac accept input from STDIN?<\/h2>\n
In case you want the tac command to accept input from the standard input, just don’t pass any file name to it.<\/p>\n
tac<\/p>\n
Once you run the command in the way mentioned above, it will wait for you to input content. Once you are done with that, press Ctrl+d to signify you’re done, and then tac will produce its output on STDOUT.<\/p>\n
Conclusion<\/h2>\n
As you can see, tac is easy to understand and work with. The number of command line options it offers is limited, and we’ve discussed most of them here. You can learn more about the command by heading to its man page<\/a>.<\/p>\n
\n
Share this page:<\/b><\/p>\n
\n\"\"<\/a>
\n\"\"<\/a>
\n\"\"<\/a>
\n\"\"<\/a>\n<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
We’ve already discussed the Linux cat command\u00a0in one of our earlier tutorials. As you may be aware, the cat command is mainly used for displaying file contents in output. However, what you may not be aware of is that there exists a command that does exactly opposite of what cat does. The tool in question …<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[36],"tags":[],"class_list":["post-4027","post","type-post","status-publish","format-standard","hentry","category-36"],"_links":{"self":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/4027","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/comments?post=4027"}],"version-history":[{"count":0,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/4027\/revisions"}],"wp:attachment":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/media?parent=4027"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/categories?post=4027"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/tags?post=4027"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}