As you start using the terminal more, you’ll be continually running a variety of commands.And then you’ll find yourself in the situation where you want to know which commands you run earlier or run a particular command again.This is why history command exists in Linux. It’s a shell built-in and extremely useful for terminal dwellers.Since it is a shell built-in, it may behave slightly differently depending on the shell you are using (bash, zsh, ksh etc) and how it was configured. Still, at the core, the basics remain the same.In this tutorial, I’ll go over the basic usage of the history command and then show some useful tips you should enjoy learning about.Check history of commandsYou can press the up key repeatedly to go through the history of commands. But it only shows one command at a time. The history command lets you see all the previously run commands.Open a terminal and run the following command:historyIt showed commands that you have run in the past. For me, it shows the following:The history is usually stored in the ~/.bash_history directory. ~ denotes the home directory, in case you didn’t know. If you are ever in doubt, you can check the HISTFILE variable to get the history file location of your shell.echo $HISTFILEHow many commands are stored in the history? That depends on the HISTFILESIZE variable. In Debian and Ubuntu, it is usually set to 2000.echo $HISTFILESIZE💡Too many lines in the history cluttering your screen? You can choose to display only the last N lines of the history with history NRunning commands from historyDid you notice that the history command shows a number in front of the command entries? You can use this number to run a command from the history. For example to run the Nth entry in the command history, use:!NHere’s an actual example where I run the commands at 152nd entry in the history.Getting more from the last run commandThis is not really a direct example of the history command but it deals with the history of commands and I wanted to discuss it.You can use the !! to get the last run command. This is extremely useful in the case when you forget to run a command with sudo. Instead of retyping the entire command, you could just use:sudo !!It will show the full command that is being run. Here’s an example:If you made a typo anywhere in the previous command, you can fix it in this fashion:^foo^barThis will replace the first foo with bar in the last run command.Here’s a practical example:💡Another tip, which is more of a terminal shortcut and may not work everywhere but still very handy. To use the last argument of the last ran command, use the Alt+. keys. Viewing a deeply nested directory with ls command and would like to switch into it? Instead of typing everything, just use cd and press Alt+.Search through the command historyYou can press up (and down) key to cycle through the command history and press enter when your desired command comes up. This works fine for the last few commands but you should not keep on pressing the up key 100 times to get the command from the history.One way to search in the history would be to filter it with grep command.Let’s say you want to look for the tail command you ran earlier:history | grep tailAnother way is to use the reverse search feature. Press Ctrl+R and you’ll find yourself in the reverse search interface. Start typing for your search term and it starts showing matching commands from the history.Of course, there can be multiple matches with the same search string. Press Ctrl+R repeatedly to cycle through all the matches. Only a single match is shown at a time.If you find the command you were looking for, press the right arrow key to exit the reverse search and start using the command.Press Ctrl+C to come out of the reverse search without getting any commands to use.Delete command from historyTo delete a command from the history, you can use its entry number in this way:history -d NIn the example below, I delete the long flatpak add command listed at number 181:You can also provide a range of lines to delete:history -d 160-180💡history -c will clear the entire bash history.Exclude some commands from the historyIf you do not want a command to be recorded in the history, just put a space before it and run:In the example below, I ran a random command that doesn’t even exist but I put space before it. It threw an error, obviously, but it is not recorded in the history.Did you notice that the second history 7 was also not recorded in the history? That’s because of the HISTCONTROL environment variable. It can have the following values:ignorespace: Run a command by putting a space before it and it won’t be included in the history.ignoredups: If there are two or more identical commands ran consecutively, only the first one gets recorded.ignoreboth: Use both of the above two mentioned features.💡You can also set the HISTIGNORE variable in the bashrc file and exclude some of the common commands from history. Use it like HISTIGNORE=’pwd:echo *:clear’Bonus: Why do some commands are not recorded in history?Have you ever noticed that not all the commands you run are recorded in history? Are you running multiple terminal sessions? That could be the culprit.Here’s the thing. The history file ~/.bash_history is not modified until you close the terminal session.If you check the history command and the content of ~/.bash_history, you’ll see that the commands you ran in the present session are not in the ~/.bash_history file.If you have ever opened multiple terminals and tabs, you might have realized that recently run commands in one tab is not available in the other tab when you press the arrow key. That’s because command history for the current session is not saved to the ~/.bash_history file yet.Now, when you start closing the terminal sessions, only the history from the last closed session is recorded. Command history from other sessions is lost. That’s the default behavior. You may change this by using the export PROMPT_COMMAND=’history -a’ (append mode) in your bashrc file. What it does is that before showing the prompt (that $ sign on the terminal), it adds the just run command to the history file.Some people use export PROMPT_COMMAND=’history -a; history -r’ which not only records the history from each session, it also fetches command history from other terminal sessions so that you can use them with the up arrow keys. It may sound good, but it quickly gets messy. Entirely up to you if you want that.ConclusionEven if don’t use the history command in the sense of typing the history command, I utilize the reverse search and the up arrow key for history search all the time. But still, it is good to know the various features the history mechanism offers.I hope you learned something new and interesting about the history command in this tutorial.