Enhancing efficiency with history
Command Line – Bash History
The versatile Bash history command can save you time and effort at the command line.
If you work in a terminal, you've likely used Bash's history
command to save yourself the trouble of retyping a command [1] (Figure 1). However, if you're like most people, your use of history
may have been confined to scrolling through the list of previously used commands. If all you are interested in are the most recently used commands, the arrow keys may be all that you need. However, the history
command is capable of doing much more and in an economical way – especially if you have a good memory. You can start by adjusting history
's environmental variables and then learn how to modify history entries for easier searching and for repurposing them using three types of editing options: event designators, word designators, and modifiers. The flexibility of all these options can be combined so that, with a little memorization, you can make the Bash history work for you to save time with minimal effort.
Environmental Variables
The history
commmand has several environmental variables. All are added or modified in .profile
or .bashrc
in your home directory, depending on the distribution. The size of the history file is limited by HISTSIZE
, which sets the number of entries in the history, and/or by HISTFILESIZE
, the maximum memory to allot for the history. Both have similar structures:
HISTSIZE=NUMBER HISTFILESIZE=NUMBER
When the maximum for either variable is reached, earlier entries are deleted and replaced by new ones. Many users' first impulse is to use a high number, such as 10,000 entries. Because the history is a text file, there should usually be no problem with how much space the history file occupies. However, too large a number can make locating entries much harder. Unless you have a clear need for such a large number, a smaller one can be more efficient. In any event, you can use Ctrl+R to cycle through entries. If you have a rough idea of where an entry might be, you can use history NUMBER
to list the entries displayed, starting with the most recent, or a specific number to go directly to the entry. You can even clear your history with the command history -c
, followed by history -w
if a long history gets too confusing. Learning designators and modifiers will also make a longer history easier to use.
Another environmental variable for history
is HISTTIMEFORMAT
. As the name suggests, this variable adds a timestamp, which can help you locate entries more easily. The format is HISTTIMEFORMAT=DATE&TIME
(Figure 2).
The date and time are structured using the common values shown in Table 1. Their use and order is a matter of choice, but you may soon consider HISTTIMEFORMAT
essential.
Table 1
Values for Setting HISTTIMEFORMAT
%d |
Day |
%m |
Month |
%Y |
Year |
%H |
Hours |
%M |
Minutes |
%S |
Seconds |
Values can also be assigned to HISTCONTROL
. A value of ignorespace
excludes any command that has a space before it, while ignoredup
ignores one of the same commands when run one after the other. If you want to use both variables, use ignoreboth
.
Event Designators
An event designator calls on a specific previous command and always starts with an exclamation mark (!
). In its simplest form, an event designator follows !
with a command's number in the history. However, as you might expect, from a user account, you cannot run a command such as apt
that can only be run as root (Figure 3). You can also call a command by how many previous commands ago it was used; for example, !-4
shows the command used four entries ago. Alternatively, you can enter a string so that !pipewire
shows the last command that contains "pipewire." You can even find a string and replace it with another. For example, if you typed
cd /home/jlw/music
you could replace the cd
command with ls
with ^cd^ls
and save yourself the trouble of retyping the path.
Word Designators
Word designators select the words from the most recent matching entry in the history. To use word designators, enter the new command and its options, followed by EVENT:!WORD-DESIGNATOR^
. For example,
less !cat:^
will replace the most recent history entry found starting with cat
with less
and then run the rest of the command in the entry using less
. The word designator can be a string or specify the word at an exact position, counting from the start of the event. For example, is the first word, 3
is the fourth word, and $
is the last. In addition, you can specify a range of words, such as 4-8
, or every word except the first using an asterisk (*
) if you recall enough to be specific.
Buy this article as PDF
(incl. VAT)
Buy Linux Magazine
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.
News
-
Linux Kernel 6.13 Offers Improvements for AMD/Apple Users
The latest Linux kernel is now available, and it includes plenty of improvements, especially for those who use AMD or Apple-based systems.
-
Gnome 48 Debuts New Audio Player
To date, the audio player found within the Gnome desktop has been meh at best, but with the upcoming release that all changes.
-
Plasma 6.3 Ready for Public Beta Testing
Plasma 6.3 will ship with KDE Gear 24.12.1 and KDE Frameworks 6.10, along with some new and exciting features.
-
Budgie 10.10 Scheduled for Q1 2025 with a Surprising Desktop Update
If Budgie is your desktop environment of choice, 2025 is going to be a great year for you.
-
Firefox 134 Offers Improvements for Linux Version
Fans of Linux and Firefox rejoice, as there's a new version available that includes some handy updates.
-
Serpent OS Arrives with a New Alpha Release
After months of silence, Ikey Doherty has released a new alpha for his Serpent OS.
-
HashiCorp Cofounder Unveils Ghostty, a Linux Terminal App
Ghostty is a new Linux terminal app that's fast, feature-rich, and offers a platform-native GUI while remaining cross-platform.
-
Fedora Asahi Remix 41 Available for Apple Silicon
If you have an Apple Silicon Mac and you're hoping to install Fedora, you're in luck because the latest release supports the M1 and M2 chips.
-
Systemd Fixes Bug While Facing New Challenger in GNU Shepherd
The systemd developers have fixed a really nasty bug amid the release of the new GNU Shepherd init system.
-
AlmaLinux 10.0 Beta Released
The AlmaLinux OS Foundation has announced the availability of AlmaLinux 10.0 Beta ("Purple Lion") for all supported devices with significant changes.