Linux’s shell saves a history of the commands you run, and you can search it to repeat commands you’ve run in the past. Once you understand the Linux history command and how to use it, it can significantly boost your productivity.
As George Santayana famously said, “Those who cannot remember the past are condemned to repeat it.” Unfortunately, on Linux, if you can’t remember the past, you can’t repeat it, even if you want to.
That’s when the Linux
history command comes in handy. It allows you to review and repeat your previous commands. This isn’t intended to just encourage laziness or save time—there’s also an efficiency (and accuracy) factor at play. The lengthier and more complicated a command is, the harder it is to remember and type without making an error. There are two types of errors: one that prevents the command from working, and one that allows the command to work, but makes it do something unexpected.
history command eliminates those issues. Like most Linux commands, there’s more to it than you might think. However, if you learn how to use the
history command, it can improve your use of the Linux command line, every single day. It’s a good investment of your time. There are far better ways to use the
history command than just hitting the Up arrow repeatedly.
The history Command
In its simplest form, you can use the
history command by just typing its name:
The list of previously used commands is then written to the terminal window.
The commands are numbered, with the most recently used (those with the highest numbers) at the end of the list.
To see a certain number of commands, you can pass a number to
history on the command line. For example, to see the last 10 commands you’ve used, type the following:
history | tail -n 10
RELATED: How to Use Pipes on Linux
If you want to reuse a command from the history list, type an exclamation point (!), and the number of the command with no spaces in-between.
For example, to repeat command number 37, you would type this command:
To repeat the last command, type two exclamation points, again, without spaces:
This can be useful when you issue a command and forget to use
sudo . Type
sudo, one space, the double exclamation points, and then hit Enter.
For the following example, we typed a command that requires
sudo. Instead of retyping the whole line, we can save a bunch of keystrokes and just type
sudo !!, as shown below:
mv ./my_script.sh /usr/local/bin/
So, you can type the corresponding number from the list to repeat a command or use the double exclamation points to repeat the last command you used. However, what if you want to repeat the fifth or eighth command?
You can use one exclamation point, a hyphen (-), and the number of any previous command (again, without spaces) to repeat it.
To repeat the 13th previous command, you would type the following:
Searching for Commands by String
To repeat the last command that starts with a particular string, you can type an exclamation point, and then the string with no spaces, and then hit Enter.
For example, to repeat the last command that started with
sudo, you would type this command:
There’s an element of danger in this, though. If the last command that started with
sudo isn’t the one you think it is, you’ll launch the wrong command.
To provide a safety net, though, you can use the
:p (print) modifier, as shown below:
history to print the command to the terminal window, rather than executing it. This allows you to see the command before you use it. If it is the command you want, press the Up arrow, and then hit Enter to use it.
If you want to find a command that contains a particular string, you can use an exclamation point and question mark.
For example, to find and execute the first matching command that contains the word “aliases,” you would type this command:
This will find any command that contains the string “aliases,” regardless of where it appears in the string.
An interactive search allows you to hop through a list of matching commands and repeat the one you want.
Just press Ctrl+r to start the search.
As you type the search clue, the first matching command will appear. The letters you type appear between the backtick (`) and the apostrophe (‘). The matching commands update as you type each letter.
Each time you press Ctrl+r, you’re searching backward for the next matching command, which appears in the terminal window.
When you press Enter, the displayed command will execute.
To edit a command before you execute it, press either the Left or Right arrow key.
The command appears on the command line, and you can edit it.
You can use other Linux tools to search the history list. For example, to pipe the output from
grep and search for commands that contain the string “aliases” you could use this command:
history | grep aliases
Modifying the Last Command
If you need to fix a typo, and then repeat the command, you can use the caret (^) to modify it. This a great trick to have up your sleeve for whenever you misspell a command or want to rerun one with a different command-line option or parameter.
To use it, type (without spaces) a caret, the text you want to replace, another caret, the text you want to replace it with, another caret, and then press Enter.
For example, suppose you type the following command, accidentally typing “shhd” instead of “sshd”:
sudo systemctl start shhd
You could correct this easily by typing the following:
The command is executed with “shhd” corrected to “sshd.”
Deleting Commands from the History List
You can also delete commands from the history list with the
-d (delete) option. There’s no reason to keep your misspelled command in the history list.
You can use
grep to find it, pass its number to
history with the
-d option to delete it, and then search again to make sure it’s gone:
history | grep shhd
history -d 83
history | grep shhd
You can also pass a range of commands to the
-d option. To delete all list entries from 22 to 32 (inclusive), type this command:
history -d 22 32
To delete only the last five commands, you can type a negative number, like so:
history -d -5
Manually Updating the History File
When you log in or open a terminal session, the history list is read in from the history file. In Bash, the default history file is
Any changes you make in your current terminal window session are only written to the history file when you close the terminal window or log out.
Suppose you want to open another terminal window to access the full history list, including commands you typed in the first terminal window. The
-a (all) option allows you to do this in the first terminal window before you open the second.
To use it, type the following:
The commands are written silently to the history file.
If you want to write all changes to the history list to the history file (if you deleted some old commands, for example), you can use the
-w (write) option, like so:
Clearing the History List
To clear all commands from the history list, you can use the
-c (clear) option, as follows:
If you additionally want to force these changes to the history file, use the
-w option, like so:
Security and the History File
If you use any applications that require you to type sensitive information (like passwords) on the command line, remember this will also be saved in the history file. If you don’t want certain information saved, you can use the following command structure to delete it from the history list immediately:
special-app my-secret-password;history -d $(history 1)
This structure includes two commands separated with a semicolon (;). Let’s break this down:
- special-app: The name of the program we’re using.
- my-secret-password: The secret password we need to provide for the application on the command line. This is the end of command one.
- history -d: In command two, we invoke the
-d(delete) option of
history. What we’re going to delete comes is in the next portion of the command.
- $(history 1): This uses a command substitution. The portion of the command contained in the
$()is executed in a subshell. The result of that execution posts as text in the original command. The
history 1command returns the previous command. So, you can think of the second command as history -d “last command here.”
You can use the
history 5 command to make sure the command containing the password was removed from the history list.
There’s an even simpler way to do this, though. Because Bash ignores lines that begin with a space by default, just include a space at the start of the line, as follows:
The command with the password isn’t added to the history list. The reason this trick works is contained within the
The .bashrc File
.bashrc file executes each time you log in or open a terminal window. It also contains some values that control the behavior of the
history command. Let’s edit this file with
Type the following:
Near the top of the file, you see two entries:
HISTSIZE: The maximum number of entries the history list can contain.
HISTFILESIZE: The limit for the number of lines a history file can contain.
These two values interact in the following ways:
- When you log in or start a terminal window session, the history list is populated from the
- When you close a terminal window, the maximum number of commands set in
HISTSIZEare saved to the
- If the
histappendshell option is enabled, the commands are appended to
- After saving the commands from the history list to
.bash_history, the history file is truncated to contain no more than
Also near the top of the file, you see an entry for the
You can set this value to do any of the following:
ignorespaces:Lines that begin with a space aren’t added to the history list.
ignoredups:Duplicate commands aren’t added to the history file.
ignoreboth:Enables both of the above.
You can also list specific commands you don’t want added to your history list. Separated these with a colon (:) and put them in quotation marks (“…”).
You would follow this structure to add a line to your
.bashrc file, and substitute the commands you want to be ignored:
If you want to add timestamps to the history list, you can use the
HISTIMEFORMAT setting. To do so, you just add a line like the following to your
export HISTTIMEFORMAT="%c "
Note that there’s a space before the closing quotation marks. This prevents the timestamp from butting up to the commands in the command list.
Now, when you run the history command, you see date- and timestamps. Note that any commands that were in the history list before you added the timestamps will be timestamped with the date and time of the first command that receives a timestamp. In this example shown below, this was command 118.
That’s a very long-winded timestamp. However, you can use tokens other than
%c to refine it. The other tokens you can use are:
%F: Full date (year-month-date format)
%T: Time (hour:minutes:seconds format)
%c: Complete date and time stamp (day-date-month-year, and hour:minutes:seconds formats)
Let’s experiment and use a few different tokens:
export HISTTIMEFORMAT="%d n%m %T "
The output uses the day, month, and time.
If we remove the day and month, though, it will just show the time.
Any changes you make to
HISTIMEFORMAT apply themselves to the entire history list. This is possible because the time for each command is stored as the number of seconds from the Unix epoch. The
HISTTIMEFORMATdirective simply specifies the format used to render that number of seconds into a human-readable style, such as:
export HISTTIMEFORMAT="%T "
Our output is now more manageable.
You can also use the
history command to audit. Sometimes, reviewing commands you’ve used in the past can help you identify what might have caused an issue.
Just as you can in life, on Linux, you can use the
history command to relive the good times and learn from the bad.
|Files||tar · pv · cat · tac · chmod · grep · diff · sed · ar · man · pushd · popd · fsck · testdisk · seq · fd · pandoc · cd · $PATH · awk · join · jq · fold · uniq · journalctl · tail · stat · ls · fstab · echo · less · chgrp · chown · rev · look · strings · type · rename · zip · unzip · mount · umount · install · fdisk · mkfs · rm · rmdir · rsync · df · gpg · vi · nano · mkdir · du · ln · patch · convert · rclone · shred · srm|
|Processes||alias · screen · top · nice · renice · progress · strace · systemd · tmux · chsh · history · at · batch · free · which · dmesg · chfn · usermod · ps · chroot · xargs · tty · pinky · lsof · vmstat · timeout · wall · yes · kill · sleep · sudo · su · time · groupadd · usermod · groups · lshw · shutdown · reboot · halt · poweroff · passwd · lscpu · crontab · date · bg · fg|
|Networking||netstat · ping · traceroute · ip · ss · whois · fail2ban · bmon · dig · finger · nmap · ftp · curl · wget · who · whoami · w · iptables · ssh-keygen · ufw|
- › How to Customize the Bash Shell With shopt
- › What Is the Bash Shell, and Why Is It So Important to Linux?
- › 4 Ways to Ruin Your Smartphone’s Battery
- › Here’s How Mozilla Thunderbird Is Making a Comeback in 2022
- › Why Do I See “FBI Surveillance Van” in My Wi-Fi List?
- › ExpressVPN Review: An Easy-to-Use and Secure VPN for Most People
- › What Can You Do With the USB Port on Your Router?
- › 10 Things Blocking Your Wi-Fi Signal at Home